Last modified: 2013-12-02 08:25:22 UTC
Git bisect gives commit e00c9872323055625ce1633d5628a37ee88c9b7f (not in gerrit) as the culprit. commit e00c9872323055625ce1633d5628a37ee88c9b7f Author: jeroendedauw <jeroendedauw@gmail.com> Date: Sat Nov 30 05:13:02 2013 +0100 Remove manual autloloading code Change-Id: Ib1f85bc7f74ab970d322be08392fa976dcd811d4
Maps no longer supports installation by cloning its git repo in this way. Same story as SMW. Either stick with the 2.x release or use Composer. This support has been removed as it cannot be maintained in a way that is convenient for the users (unless you think cloning 15 git repos is OK). And yeah, not in Gerrit. https://github.com/JeroenDeDauw/Maps/commit/e00c9872323055625ce1633d5628a37ee88c9b7f
Sorry but this is real PITA right now. You are basically forcing me to rewrite our deployment system to support two different ways of getting extensions.
Nope. I'm not forcing you to use the latest dev version.
In the mean while, can you give stable branches for all the affected extension?
Does the new composer installation workflow mean that downloading an extension via https://www.mediawiki.org/wiki/Special:ExtensionDistributor?extdist_extension=Maps does not make sense any longer?
(In reply to comment #5) > Does the new composer installation workflow mean that downloading an > extension via https://www.mediawiki.org/wiki/Special: > ExtensionDistributor?extdist_extension=Maps does not make sense any longer? As far as I understand, that is a correct assessment, Raimond.
Maps never officially supported the ExtensionDistributor, as this thing is rather arbitrary and inferior to the release tarballs that have been provided for any recent Maps release.
