Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95714
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.54 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <A7.D5.18051.896CFC75@pb1.pair.com>
References: <CANaX5nf5S6aS-ZaB=51qvXv+wbReGb2petPBDogTA+MNMHyysQ@mail.gmail.com>
 <b3bd7acf-a525-d921-1b1b-64ccf94b858b@gmail.com> <A8.67.32927.27DDBC75@pb1.pair.com>
 <CANUQDCjeH45_2aEq74CCEOY4xc3xJ0o_+yRQ2NVy0K2VdOXFBQ@mail.gmail.com>
 <C9.2F.45301.38D6EC75@pb1.pair.com> <CAH-PCH5qHdYen33Q_s7kTKM_8qK71v8Ky6kT4fzuRfAwfX06BQ@mail.gmail.com>
 <A7.D5.18051.896CFC75@pb1.pair.com>
Date: Wed, 7 Sep 2016 10:10:25 +0200
Message-ID: <CAH-PCH568TPsztkWT553QVQy7jsp1tcqT5w+OT1PoCDt-PbUOg@mail.gmail.com>
To: Tony Marston <TonyMarston@hotmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7ba9790c254190053be6729f
Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle
From: tyra3l@gmail.com (Ferenc Kovacs)

--047d7ba9790c254190053be6729f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Sep 7, 2016 at 9:49 AM, Tony Marston <TonyMarston@hotmail.com>
wrote:

> "Ferenc Kovacs"  wrote in message news:CAH-PCH5qHdYen33Q_s7kTKM_
> 8qK71v8Ky6kT4fzuRfAwfX06BQ@mail.gmail.com...
>
>>
>>
>>>
>>> Composer doesn't do that.
>>>>
>>>>
>>> Then how come I've seen several complaints in various forums about
>>> composer updating libraries in the background and screwing things up.
>>>
>>
>> That proves nothing except that your knowledge is very limited.
>>>
>>
>
>> indeed it does.
>>
>
> I can only report what I have read in various newsgroups and forums, and
> they have said that composer has screwed up their installations. If it is
> capable of doing that then it is a serious issue that needs addressing.


you can, but you shouldn't spread FUD but do your own research.
composer will only do something when you execute it, without providing any
actual problem, there is no way those could be refuted (FUD), and brings
nothing to the discussion.
what you have probably seen is people not using the tool properly
from my experience people usually screw 2 things up:

   1. executing "composer update" without any arguments which will update
   every package listed in your composer.json file to the latest version
   allowed by the version constraints
   2. not putting the composer.lock under version control and then being
   surprised that the other developer who makes a "composer install" from
   composer.json can have different(eg. more recent) versions installed


--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--047d7ba9790c254190053be6729f--