[Tickets #6587] Re: Integrate groupware PEAR-bundling into Horde base release tarballs

bugs at horde.org bugs at horde.org
Thu Apr 10 10:05:08 UTC 2008


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/6587
-----------------------------------------------------------------------
 Ticket             | 6587
 Updated By         | Gunnar Wrobel <p at rdus.de>
 Summary            | Integrate groupware PEAR-bundling into Horde base
release tarballs
 Queue              | Horde Base
 Version            | HEAD
 Type               | Enhancement
 State              | New
 Priority           | 1. Low
 Milestone          |
 Patch              |
 Owners             |
-----------------------------------------------------------------------


Gunnar Wrobel <p at rdus.de> (2008-04-10 06:05) wrote:

I guess there are two very different perspectives here: the viewpoint of a
distribution and the viewpoint of the user installing horde on a webserver
without support of package management from a distribution.

> PEAR is already tricky for distributions, since you don't get the
> same thing installing distro packages vs. using the PEAR command.
>
> And we've been burned multiple times by PEAR changes (DB.php quote(),
> etc.) when people upgrade. Distributing the supported package version
> with Horde could eliminate a lot of that.

>From the viewpoint of the distribution this is definitely the job of the
package manager. Bundled PEAR packages only cause pain from that point of
view because the least one has to do is to remove them. But I experience
plenty of additional problems with bundled PEAR packages when packaging
stuff for Gentoo. On the other hand this was often just caused by lazy devs
and that wouldn't happen with Horde.

>
> Unless we offer bundles with every single app combination or at least
> base app package (chora/whups/etc., hermes/minerva/etc.), I think a
> lot of people will use the tarballs that don't need special
> flexibility. And if they want to use their own PEAR libs they can
> adjust the include_path accordingly.

As bundled packages may be helpful for users without support of a fine
distro I wonder if it wouldn't be possible to find a compromise and simply
add a separate bundle tar.gz bundle of suggested PEAR packages. This way
people might decide if they'd like to use it or not.




More information about the bugs mailing list