Arch Linux User Repository

As per a recent out-of-date notification, I've updated this package to the last in the 2.x series. Note that when Phing v3.0 is "officially" the only stable series installation via this AUR package will no longer be supported, or it may require additional dependencies on Composer. I haven't decided, but we may opt for the latter since Composer IS in the [extra] repo.

@zancarius I agree - the best way to install phing is installed locally in project via composer.

@pdynarowski

You probably need to import the appropriate key from the PKGBUILD:

gpg --keyserver hkp://keys.gnupg.net --recv-keys 566E877A27BD4343E956BC9D2420BAE0A3BE25C6

This should be the key for mrook-at-php.net.

This PKGBUILD is behind a few patch versions, and I need to update it. Unfortunately (?), it appears that they're no longer signing new releases in the 2.x branch.

Note that as of Phing v3.0, manual installation is no longer supported[1]. I would highly recommend migrating your tooling to install Phing via composer[2] if at all possible. This PKGBUILD should be considered a last resort option to install Phing.

[1] https://www.phing.info/#install

[2] https://getcomposer.org/

I have PGP verify error - incorrect public key error

==> Weryfikowanie podpisów plików źródłowych za pomocą gpg... phing-2.16.1.phar ... NIE ZGADZA SIĘ (nieznany klucz publiczny 2420BAE0A3BE25C6) ==> BŁĄD: Jeden lub więcej podpisów PGP nie może zostać zweryfikowanych!

Okay, I've updated it, and have removed the phar.ini drop for PHP7.

Hmm, you have a point. I don't use PHP much anymore and have been avoiding the PHP7 update since it causes some breakage for legacy applications. The best option will be to remove the phar.ini since it's no longer needed. Other than that, any suggestions? When it comes to Phing, I think the "correct" way is to install it on a per-project bases via Composer, rather than using this package in the AUR. To be fair, I believe I added this warning to the package install message, and I highly recommend using Composer whenever possible. That probably means this package ought to be orphaned and/or deleted since the PEAR install is difficult to get right via AUR, and I'm not sure installing this globally is the right way to go about things either.

> $ php -m > PHP Warning: PHP Startup: Unable to load dynamic library > '/usr/lib/php/modules/phar.so' - /usr/lib/php/modules/phar.so: cannot open > shared object file: No such file or directory in Unknown on line 0 > [PHP Modules] > bcmath > .... > > $ LANG=en_US pacman -Qo /etc/php/conf.d/phar.ini > /etc/php/conf.d/phar.ini is owned by phing 2.13.0-1 This said since PHP7 Phar is builtin, thus there is no phar.so anymore. After every phing update I see this error coming up again. Anyway, I don't think it's the right way, that one package changes another tools global configuration. Print a warning, if you find you need a different configuration, but don't change it yourself.

It appears this is actually due to a recurring bug in PEAR's installroot/packagingroot that has surfaced (and resurfaced) since 2005, 2006, 2009, and 2010. Neither of these options seem to work as the documentation suggests, so either my understanding is wrong and everyone who has filed bugs on PEAR is out of their collective minds or it just doesn't work. The installation of Phing via this PKGBUILD worked on my system because I've had other PEAR packages installed from many moons ago, thus having already created the /usr/share/pear/.lock file (incidentally, touching that file as root would have allowed the package to continue installing for you--but that's not a polite requirement). Personally, I think PEAR is a piece of crap, but that's neither here nor there. As it turns out, Phing has been offering for a while now the option of downloading the pre-built PHAR as a stand-alone archive. I've shifted the PKGBUILD over to use that instead of building via PEAR and packaging it henceforth. It should work now for you and drop me a line if it doesn't. You don't need to worry about phar support--the PKGBUILD will drop an .ini enabling the extension in /etc/php/conf.d/phar.ini, but if that doesn't work you may have to enable it manually. Though, I still recommend installing Phing per-project via Composer.

Latest version does not work 'cause of access rights. /usr/share/pear directory is writable only under root by default: Warning: touch(): Unable to create file /usr/share/pear/.lock because Permission denied in PEAR/Registry.php on line 835 PHP Warning: touch(): Unable to create file /usr/share/pear/.lock because Permission denied in /usr/share/pear/PEAR/Registry.php on line 835 PHP Stack trace: PHP 1. {main}() /usr/share/pear/pearcmd.php:0 PHP 2. PEAR_Command_Common->run() /usr/share/pear/pearcmd.php:307 PHP 3. PEAR_Command_Install->doInstall() /usr/share/pear/PEAR/Command/Common.php:271 PHP 4. PEAR_Registry->channelExists() /usr/share/pear/PEAR/Command/Install.php:536 PHP 5. PEAR_Registry->_lock() /usr/share/pear/PEAR/Registry.php:1590 PHP 6. touch() /usr/share/pear/PEAR/Registry.php:835