Re: [RFC] Deprecate PEAR/PECL & Replace withcomposer/pickle
| From: | Lester Caine | Date: | Thu, 08 Sep 2016 14:13:27 +0000 |
| Subject: | Re: [RFC] Deprecate PEAR/PECL & Replace withcomposer/pickle | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-95797@lists.php.net to get a copy of this message | ||
On 08/09/16 13:26, Niklas Keller 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?
>
> Why does it seem not right? It's perfectly right and the way to go if
> you're using Composer.
>
> An alternative would be to use Composer's global require and adding the
> global "bin" directory of Composer to your PATH variable.
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?
> And I
> would expect different installations of composer will affect that
> installation?
>
> What do you mean by "affect that installation"?
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.
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk