Hi,

>> == Changes since 1.24.0-rc.2 ==
>> * The composer.json file has been renamed to composer.json.sample after
>>   Jamie Thingelstad reported that his composer.json was overwritten by
>>   the tarball.

I had the same issue not aware that MW has replaced my existing
composer.json and by the time I realized it was already to late (doing
a `composer update` which costs me some considerable development
effort).

Despite this, I think we should stick to the `composer.json` and for
users that already have a `composer.json` in place make sure that they
migrate the content so that they don't loose any package by simply
replacing the file.

In future, if changes are required to the `composer.json`, please
merge instead of a simple replace and keep the user free from pain.

Cheers

On 11/26/14, Stephan Gambke <s7ep...@gmail.com> wrote:
> On 25 November 2014 at 04:13, Mark A. Hershberger <m...@nichework.com> wrote:
>> I am happy to announce the final release candidate for MediaWiki 1.24.0.
>> Download links are given at the end of this email.  There won't be any
>> more RC candidates before a final release on Wednesday unless someone
>> finds a really critical error.
>>
>> == Changes since 1.24.0-rc.2 ==
>> * The composer.json file has been renamed to composer.json.sample after
>>   Jamie Thingelstad reported that his composer.json was overwritten by
>>   the tarball.
>
> I have to agree with Legoktm.
>
> Quote from
> https://www.mediawiki.org/wiki/Manual:Upgrading#Using_a_tarball_package:
> "You should put the decompressed tarball in a new and empty folder on
> your server. If you instead extract the new version directly on top of
> your old version, rather than in a new directory, you should follow
> #Back up existing files and the database: otherwise, if you've made
> any customizations you may erase them in a way that leaves you with no
> reference to re-apply them from."
>
> Also, this will complicate installation instructions for every
> extension and skin that uses composer. They will now have to
> distinguish between two possible baselines which is a hassle for
> developers but more importantly a source of confusion for users.
>
> 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

Reply via email to