Looks like the sha256sum is incorrect (perhaps upstream re-submitted to PEAR)
Search Criteria
Package Details: php-codesniffer 3.10.3-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/php-codesniffer.git (read-only, click to copy) |
---|---|
Package Base: | php-codesniffer |
Description: | PHP_CodeSniffer tokenizes PHP, JavaScript and CSS files to detect and fix violations of a defined set of coding standards. |
Upstream URL: | https://github.com/PHPCSStandards/PHP_CodeSniffer |
Licenses: | BSD |
Submitter: | None |
Maintainer: | sender |
Last Packager: | sender |
Votes: | 63 |
Popularity: | 0.000005 |
First Submitted: | 2010-06-13 09:00 (UTC) |
Last Updated: | 2024-09-23 10:14 (UTC) |
Dependencies (1)
Required by (10)
Sources (5)
biinari commented on 2015-12-10 15:30 (UTC)
biinari commented on 2015-12-10 15:25 (UTC)
@vohof You can put your additional coding standards whereever you like and configure PHP Codesniffer to find them using
phpcs --config-set installed_paths /path/to/wpcs
(replace /path/to/wpcs with the path where you put your extra coding standards) as per instructions in https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards#standalone
vohof commented on 2015-05-09 05:25 (UTC)
Hi, where do I install additional coding standards? e.g. https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards
sender commented on 2015-04-09 10:16 (UTC)
@ram4nd Can you clarify? Is it a problem with the php-codesniffer or with the custom coding style rule set that you use? After some experimenting I believe it to be the latter. Suggestions are welcome.
ram4nd commented on 2015-04-09 07:36 (UTC)
Does not work with PhpStorm!
bugbuster commented on 2015-04-05 14:24 (UTC)
I found the reason:
My user account has a .pearrc which defines custom directories. This .pearrc is picked up by the build and everything is screwed up.
I did not get -u working to skip user configuration. So I ended up using
HOME=/tmp pear install -P ${pkgdir} ${srcdir}/${_pkgname}-${pkgver}.tgz
which worked ;-)
sender commented on 2015-04-04 21:33 (UTC)
@bugbuster I can't reproduce this error. Other packages installing through PEAR apply similar techniques to remove PEAR metadata from $pkgdir. Suggestions are welcome.
bugbuster commented on 2015-04-04 10:20 (UTC)
The PKGBUILD does not work as expected:
LANG=en_US.UTF-8 makepkg
==> Making package: php-codesniffer 2.3.0-1 (Sat Apr 4 12:18:07 CEST 2015)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found PHP_CodeSniffer-2.3.0.tgz
==> Validating source files with md5sums...
PHP_CodeSniffer-2.3.0.tgz ... Passed
==> Extracting sources...
==> Removing existing $pkgdir/ directory...
==> Entering fakeroot environment...
==> Starting package()...
install ok: channel://pear.php.net/PHP_CodeSniffer-2.3.0
/tmp/php-codesniffer/PKGBUILD: line 24: cd: /tmp/php-codesniffer/pkg/php-codesniffer/usr/share/pear: No such file or directory
==> ERROR: A failure occurred in package().
Aborting...
Durag commented on 2015-04-02 22:08 (UTC)
2.3.0 is out. md5sum is 7572350670346fe9183259d7c0c91656
If you also get a PHP Warning about open_basedir restrictions, I found an easy tutorial how to fix this: https://jfabianpe.wordpress.com/2012/07/03/codesniffer-en-arch-linux/
It's in spanish but easy to understand.
Pinned Comments
sender commented on 2024-07-25 10:59 (UTC)
In case of problems with GPG key try:
gpg --keyserver keys.openpgp.org --recv-keys 689DAD778FF08760E046228BA978220305CD5C32
Thanks @bickman2k, @system7