[php-maint] Bug#458436: Bug#458436: Bug#458436: php-pear doesn't warn when modules are upgradeable

[Ondřej Surý]

tags 458436 +wontfix
severity 458436 wishlist
thank you

On Fri, Mar 21, 2008 at 23:00, Josip Rodin <joy at debbugs.entuzijast.net> wrote:
> severity 458436 normal
> thanks
>
> Hi,
>
>> severity 458436 wishlist
>> thanks
>>
>> Since the PEAR packages provided by de Debian package are
>> updated/upgraded this is not a bug but a feature request.
>> Your suggestion on using debconf shouldn't be followed because debconf
>> shouldn't be used for those kind of things, NEWS.Debian should be used
>> instead.
>
> First off, please use the right address when you wish to talk to submitters,
> your message never reached me because it was sent to the bug address only.
>
> I disagree on the wish part - the whole purpose of the pear package is to
> get those external PEAR packages. If pear is used to put those files on
> users' systems, it also has the responsibility to take care of them once
> they're there. The tool itself does do that, but the package doesn't
> properly integrate with it. If we lower the bar for package quality to
> the level where one only has to ship the binaries and be done with it,
> then integration of software features with package features is a "wish",
> but it's 2008...

If you install custom packages into /usr/local/ using gcc as a compiler,
you also don't get a warning when shared library is upgraded. That's exactly
same situation as with PEAR package. If you install anything by hand, then
it's your responsibility as a system administrator to get them upgraded.

Thus I am here with Raphael on a wishlisting this bug. PEAR was not really
made to integrate well packaged (/usr) and external (/usr/local) packages, so
it's very hard to solve this.

This said we would certainly welcome a patch which would allow us to manage
packaged and non-packaged PEAR package separately, but I think this is something
which needs to be done upstream.

O.
-- 
Ondřej Surý <ondrej at sury.org>