JanZerebecki added a comment. But manually copying the dependencies of more than a dozen components (Wikibase alone has more direct dependencies) and even recursively for their dependencies does not seem a good way to improve this. The current build process is fully automated. So in the long run something like https://github.com/wikimedia/composer-merge-plugin seems like a better idea than manually doing this. But even then we would probably run composer in the CI of individual extensions and only replace it by a build when testing release branches, as otherwise we can't test changes to the dependencies before making a building with that change. Or is there something i'm missing that would allow us to not run composer?
TASK DETAIL https://phabricator.wikimedia.org/T88436 REPLY HANDLER ACTIONS Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign <username>. EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: JanZerebecki Cc: Legoktm, bd808, JanZerebecki, adrianheine, JeroenDeDauw, hashar, Aklapper, Wikidata-bugs _______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
