Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:95768 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 58310 invoked from network); 8 Sep 2016 07:43:54 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Sep 2016 07:43:54 -0000 X-Host-Fingerprint: 90.255.2.72 unknown Received: from [90.255.2.72] ([90.255.2.72:10665] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3E/80-36123-BA611D75 for ; Thu, 08 Sep 2016 03:43:42 -0400 Message-ID: <3E.80.36123.BA611D75@pb1.pair.com> To: internals@lists.php.net References: In-Reply-To: Date: Thu, 8 Sep 2016 08:43:25 +0100 Lines: 2 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Newsreader: Microsoft Windows Live Mail 16.4.3564.1216 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3564.1216 X-Posted-By: 90.255.2.72 Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle From: TonyMarston@hotmail.com ("Tony Marston") "Ferenc Kovacs" wrote in message news:CAH-PCH568TPsztkWT553QVQy7jsp1tcqT5w+OT1PoCDt-PbUOg@mail.gmail.com... > >On Wed, Sep 7, 2016 at 9:49 AM, Tony Marston >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 Perhaps users could be prevented from making such basic mistakes if they had a 21st century web interface instead of the archaic command line. -- Tony Marston