Re: solution for those depending on PEAR packages with non-PEAR
| From: | Lukas Smith | Date: | Sun, 24 Apr 2005 11:05:37 +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 12 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-37397@lists.php.net to get a copy of this message | ||
Pierre-Alain Joye wrote:
On Sun, 24 Apr 2005 12:59:48 +0200 Lukas Smith <lsmith@php.net> wrote:I rest my case. Anyways we have thrown around our arguments suffcientlycand I respect your opinion. Unless new things pop up I think I will refrain from joining this discussion again. regards, LukasPierre-Alain Joye wrote: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?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).