Re: solution for those depending on PEAR packages with non-PEAR
| From: | Pierre-Alain Joye | Date: | Sun, 24 Apr 2005 11:04:10 +0000 |
| Subject: | Re: solution for those depending on PEAR packages with non-PEAR | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-37396@lists.php.net to get a copy of this message | ||
On Sun, 24 Apr 2005 12:59:48 +0200
Lukas Smith <lsmith@php.net> wrote:
> Pierre-Alain Joye wrote:
>
> > A permanent fork will require a new name, most of the
> > licences/copyright require that. Then there is no problem at
> > all.
> >
> > Bundling does not have any problem neither. As stated by Greg
> > and as nearly all major linux distributions do using their own
> > packages repository.
>
> bundling means that your users will never know if they get the
> original package or not, something i find to be very unfortunate
> (after a while even the person that bundled may even forget if
> its unmodified code or not).
Clarify it in your documentation and change logs. How do you know if
your glib on Suse 9.3 is a modified one or not?
> bundling also creates more work for the packager.
Oh what a pain :)
--Pierre