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
dan...@honestempire.com
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
