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

From:	Rowan Collins	Date:	Thu, 08 Sep 2016 14:40:01 +0000
Subject:	Re: [RFC] Deprecate PEAR/PECL & Replace withcomposer/pickle
References:	1 2 3 4 5 6 7 8	Groups:	php.internals
Request:	Send a blank email to internals+get-95799@lists.php.net to get a copy of this message

On 08/09/2016 15:13, Lester Caine wrote:

bash: ./vendor/bin/phpcs: No such file or directory Which I presume means I do need to set up some path, but currently I no idea where 'composer global require "squizlabs/php_codesniffer=*"' has put it?

That's the directory where it goes if you *don't* use "--global": the vendor directory of the current project. The "--global" documentation refers to COMPOSER_HOME as the location it uses, which is documented here: https://getcomposer.org/doc/03-cli.md#composer-home It boils down to (I think) "~/.composer/vendor/bin/phpcs"

Currently having followed the installation guide I have things working on a home directory. This is probably what people expect today, but I still expect tools to be available which ever login I use ... testing different client profiles.

You could also just create a composer.json file in /usr/share somewhere and run "composer install" there. You could then make a symlink from /usr/bin/phpcs to wherever the executable is, and it would be in every user's default path as well.