To enable extensions to declare a version constraint on MW, so an incompatible version of an extension is not installed in the first place instead of crashing MW later on.
Stephan
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, November 15, 2019 4:27 PM, Florian Schmidt florian.schmidt.welzow@t-online.de wrote:
Extensions can express a dependency to mediawiki core in their extension.json. not sure where, how and why a non-existing composer package should be injected to a composer run.
Am 15.11.2019 10:15 schrieb David Barratt dbarratt@wikimedia.org:
as far as I know, extensions shouldn't be declaring a dependency on MediaWiki in composer.json and if one is, it should probably be fixed.
On Fri, Nov 15, 2019 at 9:50 AM Stephan Gambke via Wikitech-l < wikitech-l@lists.wikimedia.org> wrote:
When running `composer update` MediaWiki injects a mediawiki/mediawiki package, so extensions can declare a dependency on a particular MW version range. However, when doing a `composer update --dry-run` this package gets not injected causing the dry run to fail.
Does anybody know a solution/workaround?
Stephan
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
wikitech-l@lists.wikimedia.org