[PEAR-DEV] Re: [dev] Re: Horde Browser.lib and Crypt_PGP

[Eric Rostetter]

Quoting "Damian Fernandez Sosa (DESC)" <damlists at cnba.uba.ar>:

> > larger. Until very recently, forcing those users to install PEAR packages
> > *significantly* increased the difficulty of successfully installing Horde.

Mostly because the base PEAR base kept changing (one day it included LOG,
the next day it didn't, etc).  I'm hoping that since it is finally in
release now, it will not remove things willy-nilly any more.

> Shoudn't be fixed this by making a dependency check (and  installer) php
> script?
> if that script finds that this installation has an older version or PEAR
> packages (based on a xml config file) auto-install them?

Possibly breaking all your other PEAR-dependent apps that require the older
version since the PEAR module may not be backwards compatible or may conflict
with your code?

And where is this "universal auto-upgrade" script that will cleanly upgrade
the PEAR across platform?

> > The PEAR community, however, seems to want control of the code instead.
> > Hopefully I'm wrong about this or it will change, but that is the
> > impression I keep getting every time I mention this.
> >
>
> I think that the code is controlled by its developers.

Not at the level of installation support (e.g. LOG being in then out of
the default set, etc).

--
Eric Rostetter
The Department of Physics
The University of Texas at Austin

Why get even? Get odd!