On Tue, Jul 2, 2013 at 4:22 PM, Daniel Friesen <[email protected]>wrote:
> On Tue, 02 Jul 2013 09:30:57 -0700, Jeroen De Dauw <[email protected]> > wrote: > > 2. Installing extensions leaves the composer.json file modified. >> >> When installing one or more extensions via Composer, they will get added >> to >> the require section in composer.json. composer.json is not in the >> gitignore >> list. So you might well run into conflicts here, and in any case will have >> a modified file that is tracked in your git repo, which is annoying. In >> case of extension installation via LocalSettings, this stuff is in a file >> that is in gitignore. We could just add composer.json there as well, but >> this means that when we make changes to it on master, people will not get >> them any time soon. This is problematic in case we where to make MW core >> dependent on other packages, though this seems unlikely to happen, and is >> thus perhaps just a theoretical concern. Does anyone see a way around this >> problem better than putting composer.json in gitignore? Any concerns with >> putting it in gitignore? >> > > This is precisely one of the reasons I thought installing MW extensions > via Composer was a stupid idea in the first place. Installing extensions > should not require the file that MediaWiki declares it's library > dependencies and information about itself to be modified. > We can't be the only people in the world with this problem. Instead of abandoning an excellent attempt by the PHP community to provide alternatives to NIH can we lend some expertise in solving the issue instead? > Another one is extension assets. Have you dealt with the fact that MW > doesn't have a proper path to serve the css/js in debug mode, images to IE, > and other assets that an extension needs. > > ditto Erik Bernhardson _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
