Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95800
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain honestempire.com designates 66.111.4.28 as permitted sender)
Message-ID: <1473346524.1460168.719658521.3787EBE6@webmail.messagingengine.com>
To: internals@lists.php.net
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
In-Reply-To: <e8584697-8efe-e933-ca74-a404c92c30ec@lsces.co.uk>
References: <CANaX5nf5S6aS-ZaB=51qvXv+wbReGb2petPBDogTA+MNMHyysQ@mail.gmail.com>
 <04998da0-6344-0b8b-c69a-411400e340ba@lsces.co.uk>
 <1473323097.1378681.719308017.2139F909@webmail.messagingengine.com>
 <8493a9dd-1f0e-f15f-3651-0278cf25234b@lsces.co.uk>
 <ec690b39-00d3-b2f7-60e7-5dd5b30cd7b3@gmx.de>
 <e8584697-8efe-e933-ca74-a404c92c30ec@lsces.co.uk>
Date: Thu, 08 Sep 2016 15:55:24 +0100
Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace withcomposer/pickle
From: daniel@honestempire.com (Daniel Morris)

On Thu, 8 Sep 2016, at 01:13 PM, Lester Caine wrote:
> That is the chicken ... if you ARE already composer user then it will
> make some sense, but pear gives a phpcs -h which works out of the box.
> ./vendor/bin/phpcs -h does not sound right as an alternative? And I
> would expect different installations of composer will affect that
> installation?

If I run `composer global require "squizlabs/php_codesniffer=*"`, I get:

```
Changed current directory to /Users/dmorris/.composer
./composer.json has been created
Loading composer repositories with package information
Updating dependencies (including require-dev)
  - Installing squizlabs/php_codesniffer (2.7.0)
    Downloading: 100%         

Writing lock file
Generating autoload files
```

Composer has indicated in its output where the executables have been
downloaded to, I could just add `~/.composer/vendor/bin` to my `$PATH`
and then it essentially works the same way as PEAR. I generally prefer
to have project specific dependencies though, as do most others, I
believe.

This thread has turned into a Composer help/support thread now, which
I'm sure is not the original intention. I'd like to see the deprecation
of PEAR, it served many well for a long time, but Composer has made life
much easier for the majority.

--
Daniel Morris
daniel@honestempire.com