On 11/06/14 22:26, Tim Starling wrote:
One thing that concerns me about the proposed composer setup, that I
haven't mentioned yet, is the nesting of the project hierarchy, with
mediawiki/core/vendor inside mediawiki/core.
You know that we have mediawiki/extensions instead of
mediawiki/core/extensions -- that makes it easy to check out all
Gerrit repos in the natural directory hierarchy and to still have a
clean $IP/extensions which you can use for installer testing or whatever.
I wonder if a similar solution is possible with vendor -- could we
have mediawiki/vendor instead of mediawiki/core/vendor? Then it would
be possible to play around with dropping things into $IP/vendor while
still having the "vendor" git repo checked out in a sensible location,
available for editing.
-- Tim Starling
Actually, I like the sound of this. The extensions thing is sane (well,
relatively) and useful. This would also perhaps be sane.
Hopefully we won't wind up with an explosion of these pocket
repositories down the road, though, especially necessary ones...
technically none of them are actually necessary currently, and I don't
think we want core to eventually just be replaced by a meta repository
of a whole bunch of component repositories that then have all their own
component dealies and fish and squid and a bunch of goats scattered
throughout?
Or... something.
-I
_______________________________________________
Wikitech-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
