Re: [RFC] Deprecate PEAR/PECL & Replace with composer/pickle

Sent: Thursday, September 08, 2016 9:15 AM >To: Tony Marston >Cc: PHP Internals >Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle > > >On Thu, Sep 8, 2016 at 9:43 AM, Tony Marston <TonyMarston@hotmail.com> wrote: > >"Ferenc Kovacs" wrote in message >news:CAH-PCH568TPsztkWT553QVQy7jsp1tcqT5w+OT1PoCDt-PbUOg@mail.gmail.com... > > >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 > > >Perhaps users could be prevented from making such basic mistakes if they had a 21st century web >interface instead of the archaic command line. > >perhaps, or perhaps they would misclick, but now you are again trying to divert the discussion >from actual problems to the land of FUD. Have you considered the fact that some users think that the idea of being forced to use a command line interface *IS*a problem? Just because YOU like it is no reason to force your personal choice on everyone else. -- Tony Marston