Agreed; "mobilefrontend" and "mobilefrintend-tests" would probably work as a pair, same with cirrus etc. however the list of roles is getting kinda long and may need a better display with descriptions and search in the future... If we add lots more extensions *and* their optional tests or configs it's going to be a lot. :)
-- brion
On Saturday, August 9, 2014, Chad innocentkiller@gmail.com wrote:
On Sat, Aug 9, 2014 at 3:40 PM, Max Semenik <maxsem.wiki@gmail.com javascript:;> wrote:
Currently a lot of our extension Vagrant roles are working like Swiss knives: they do everything possible to imagine. For example,
MobileFrontend
always installs 3 optional dependencies while CirrusSearch includes its configuration for unit tests that among other things enforces $wgCapitalLinks = false which is untypical for most MW installs.
I hate that stupid config file for Cirrus. HATE HATE HATE.
I think many of these actually make development harder. Solution? Can we split some larger roles to "basic" and "advanced" parts, so that people
who
need an extension to play around or to satisfy a dependency will not be forced to emulate a significant part of WMF infrastructure?
Not a bad idea. Cirrus doesn't depend on half the things it says it does unless you're wanting to run browser tests.
-Chad _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org javascript:; https://lists.wikimedia.org/mailman/listinfo/wikitech-l