On Tue, Jul 2, 2013 at 12:30 PM, Jeroen De Dauw <[email protected]>wrote:
> It also needs to happen after the start of LocalSettings, > since some extensions need the core configuration to be set already or > require the user to define things before they get included. > This is an issue with the extensions. The expectation for extensions is that when the extension file is included MediaWiki is not set up. If an extension needs to do things *after* MW is set up, it should be adding a callback to $wgExtensionFunctions, which is called from the end of Setup.php. Does anyone see a way around this > problem better than putting composer.json in gitignore? Any concerns with > putting it in gitignore? Not sure on how to solve this one. It's especially troublesome for people who don't use git (i.e., they just extract the tarballs to upgrade, which means composer.json will just be completely overwritten). The best command to use for installation of an extension when you already > have MediaWiki seems to be "composer require", for instance "composer > require ask/ask:dev-master". When using this command, apparently the > require-dev packages are also installed. That's weird. There's no way to install the non-dev of an extension? *-- * *Tyler Romeo* Stevens Institute of Technology, Class of 2016 Major in Computer Science www.whizkidztech.com | [email protected] _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
