PHP packaging question: pear or not pear ?

Patrick MONNERAT pm at
Thu Feb 3 11:32:06 UTC 2011

On Wed, 2011-02-02 at 19:20 +0100, Remi Collet wrote: 
> Le 02/02/2011 14:09, Patrick MONNERAT a écrit :
> > 
> > There is a project I would like to package: this is
> > This project is using PEAR support
> > and assumes a PEAR installation (in the Auth subdirectory), but it is
> > NOT available from the PEAR repository at
> > 
> > Should I package it as pear package (i.e.: php-pear-Auth-Yubico) and
> > keep the intended installation location, or should I call it php-yubico
> > and relocate the modules under /usr/share/php with a php-pear
> > requirement ? The PHP packaging guidelines are not very clear for this
> > particular case.
> I think you can package this package as php-pear-Auth-Yubico.
> It provides a package.xml so you can install it as any other pear
> extension, and register/unregister it during post/postun scriplet.
> You just need to use the special default __uri channel.
> You can look at php-pear-CAS which an example of such a package.

Many thanks for the info. This means there is no need for a project to
be available from the PEAR repository to be packaged as php-pear-*: I
think this would be good to be mentioned in the packaging guidelines.

> P.S. you can put me in CC of the review.

:-) will do !


More information about the devel mailing list