Heiya Ad,
that's true. Indeed, this is another way to say it. :)
Cheers Karsten
Am 12.11.2016 um 14:29 schrieb Ad Strack van Schijndel:
Hi Karsten,
Ok, so it is better to use composer.local.json for the extensions as well. The composer equivalent of the LocalSettings.php.
Is that it?
Ad
On 11 Nov 2016, at 15:58, kghbln mediawiki@kghoffmeyer.de wrote:
Heiya Ad,
in contrast to "composer.local.json" the "composer.json" file gets overwritten on every update or upgrade, so you will have to recreate this file every time (four to six times a year). This does not happen to "composer.local.json".
Cheers Karsten
Am 11.11.2016 um 07:19 schrieb Ad Strack van Schijndel:
I'll try to keep up with you.
Why can't Guzzle be installed with composer.json? I put other libraries in there as well...
Ad
Op 11 nov. 2016 om 01:16 heeft Mark A. Hershberger mah@nichework.com het volgende geschreven:
Ad Strack van Schijndel writes:
Same here! Busy with other things. But although this topic is not urgent it is definitely important.
I'm making an effort to get on top of things here. Hence, the “early” reply.
Actually we have 2 use cases: one inside the MW framework and one outside. Is it possible/wise to use the Guzzle library for both?
It is certainly possible, especially now that you have composer.local.json to install Guzzle with inside of MediaWiki. Since Guzzle uses the namespace \GuzzleHttp, you shouldn't have a problem with conflicting names inside MW.
It seems like you'd only need to use one set of APIs this way, which is a bonus!
Mark.
-- Mark A. Hershberger NicheWork LLC 717-271-1084
Mediawiki-enterprise mailing list Mediawiki-enterprise@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise
Mediawiki-enterprise mailing list Mediawiki-enterprise@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise
Mediawiki-enterprise mailing list Mediawiki-enterprise@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise