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

[Mark A. Hershberger]

Steve Langasek <vorlon at debian.org> writes:

> Correct me if I'm wrong, but I don't see any reason that we need to care
> about local-and-pear vs. local-and-not-pear for Debian.

As a sysadmin, I see a huge reason for caring about local vs. “vendor”
PEAR packages.  I really appreciate the way CPAN modules, for example,
are kept the local modules separate from the debianized ones.  In fact,
I tend to use dh-make-perl to create packages instead of just running
CPAN from the command line.

For the same reason, I prefer having pear modules packaged up in
re-installable form so that I don't have to repeat my work (even if it
is just “pear install”).  Keeping locally installed PEAR modules
separate would allow me to see, at a glance, what software needs to be
packaged up.

> If the local admin feels a need for a local php path that's guarded
> against pear interference they can always add one, and if there's
> enough demand we can always update the policy to include it later.

Why not do it now?  From my point of view the advantage is obvious.

Mark.

-- 
http://hexmode.com/
GPG Fingerprint: 7E15 362D A32C DFAB E4D2  B37A 735E F10A 2DFC BFF5

The most beautiful experience we can have is the mysterious.
    -- Albert Einstein, The World As I See it