[php-maint] up-to-date policy for PHP PEAR modules

[Steve Langasek]

On Tue, Sep 18, 2007 at 12:33:15AM +0200, Gregory Colpart wrote:
> On Mon, Sep 17, 2007 at 08:51:04AM +0200, sean finney wrote:

> > > Feel free to comment it and send me updates by mail or IRC.
> > > The main idea is to have similar packaging for all modules to
> > > make easier collaborative maintenance. I hope this could also
> > > permit to "foo web application" maintainer to ask for new modules
> > > instead of packaging and take the responsability to maintain it.

> > while you're at it, do you have any thoughts/suggestions for how we should 
> > deal with having both debian-packaged pear modules and locally installed pear 
> > modules (i.e. pear install foo) on the same system?  in perl they have a 
> > solution for this by having multiple directories (i.e. site-perl and vendor), 
> > but we currently don't have anything like that for pear, which has always 
> > been a problem (and i don't believe this is.

> I think /usr/share/php/ should be only for debian-packaged pear
> modules and locally installed pear modules should go to
> /usr/local/php/ or whatever directory (similar to perl policy).
> We should probably change a few things to make easier the deal
> between debian-packaged and local pear modules (create empty
> /usr/local/php/ dir, set include_path to
> '.:/usr/local/php:/usr/share/php' in php.ini, perhaps write a
> /usr/bin/pear-local wrapper, etcetera)

/usr/local/share/php, not /usr/local/php; but yes, otherwise correct.

The current pear package seems to pear install to /usr/share/php, cluttering
directories that are supposed to be under dpkg control.  Grr.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon at debian.org                                   http://www.debian.org/