Home » PHP » PHP_CodeSniffer » Bug #9837
no phpcs
Details
| Submitted | 2007-01-15 11:59 UTC |
|---|---|
| From | tobias at code-x dot de |
| Assigned | squiz |
| Status | Bogus |
| Package | PHP_CodeSniffer |
| PHP Version | 5.2.0 |
| Roadmaps | (Not assigned) |
Comments
[2007-01-15 11:59 UTC] tobias at code-x dot de
Description:
------------
i installed it doing the following command as root
pear install -f PHP_CodeSniffer
downloading PHP_CodeSniffer-0.3.0.tgz ...
Starting to download PHP_CodeSniffer-0.3.0.tgz (138,246 bytes)
..............................done: 138,246 bytes
No handlers for package.xml version 2.0
after that i run whereis phpcs
whereis phpcs
phpcs:
or only phpcs
-bash: phpcs: command not found
whats wrong?
[2007-01-15 22:13 UTC] squiz at php dot net
The phpcs script will be installed into your PEAR bin directory. You can find this directory by running:
pear config-show
and looking at the line that says bin_dir. The directory there is where the file "phpcs" will be installed.
Please check inside that directory to see if it was installed correctly. If it is, you'll need to make sure that the bin_dir is in your path.
[2007-01-15 22:25 UTC] squiz at php dot net
Sorry I didn't see this before, but PEAR is giving you an error message:
No handlers for package.xml version 2.0
PHP_CodeSniffer uses package.xml version 2. You must have an older version of PEAR that does not support this versions.
Please update your PEAR installation and try again.
[2007-01-15 22:27 UTC] squiz at php dot net
Probably should have mentioned how to udpdate PEAR :)
pear upgrade PEAR
[2007-01-15 22:27 UTC] squiz at php dot net
Probably should have mentioned how to update PEAR :)
pear upgrade PEAR
[2007-01-19 05:48 UTC] squiz at php dot net
Sorry, but your problem does not imply a bug in PEAR itself. For a
list of more appropriate places to ask for help using PEAR, please
visit http://pear.php.net/support/ as this bug system is not the
appropriate forum for asking support questions.
Thank you for your interest in PEAR.
I'm closing this bug because I'm pretty sure there is nothing wrong with PHP_CodeSniffer itself. The previous comments explain how to resolve this issue.