Re: solution for those depending on PEAR packages with non-PEAR

Pierre-Alain Joye wrote:

On Sat, 23 Apr 2005 22:22:14 -0400 greg@chiaraquartet.net (Greg Beaver) wrote:

um, no. Read the proposal. It's not a "permanent fork" - it's a one-shot uri-based package that is overwritten by the next release.

Or how to be sure that this one-shot replacement will not break other applications? How do you prevent one to do not provide a permanent fork? --Pierre

First, this is mostly for use inside a specific environment. Like if I use HTML_QuickForm for work and I wish to use CVS and have it install it automatically, I can just package current CVS and link to that on our servers. I know that I won't break other stuff because I'm in control of said other stuff. I do however, think that this is valid concern, and that if its done it should have a severe warning, something like: ============== This package patches pear.php.net/Foo version 1.2.0 from uri http://www.example.com/Foo-1.2.0.1.tgz because of Critical Bug in Bar(), do not install unless you trust this source. **Warning:** This may break code that relies on the behaviour of pear.php.net/Foo-1.2.0, only install if you are sure this is not the case. Install? [Yn] ============== I also think its use in PEAR should be strongly discouraged, but it can be used if necessary. Its use should be pre-approved by a QA member *before* release. Failure to do this will result in the released being withdrawn with no prior notice to the developer. - Davey