Re: PEAR_ErrorStack Quality
| From: | Greg Beaver | Date: | Sun, 04 Jul 2004 15:37:23 +0000 |
| Subject: | Re: PEAR_ErrorStack Quality | ||
| References: | 1 2 3 | Groups: | php.pear.core |
| Request: | Send a blank email to pear-core+get-427@lists.php.net to get a copy of this message | ||
Stephan Schmidt wrote:
Hi, Stefan Neufeind, PEAR wrote:Right. The loophole for PEAR_ErrorStack is that PEAR 1.3 does not use it, and the release notes clearly state that it is included only to help with experimentation and stabilizing of the PEAR_ErrorStack package. PEAR 1.4 (which is devel) uses PEAR_ErrorStack. I don't like including it this way, but there was no other good way to do it with PEAR 1.3. Note the incredible difficulties with using Console_Getopt - any BC break in the package breaks pear upgrade pear. We need to be able to specify required packages that will be installed as if they are part of the distribution, with recommended version numbers. Upgrade to a newer version number would require a --force. I am happy to help work out what is needed for this, but it will require at least as much work as implementing channels. This makes it a version 1.5 feature or version 2.0 feature at the earliest. GregI don't remember if there is anything in the docs yet, however I'm sure this was commonly agreed upon already in the discussions. Imho you're right ... we can't run stable with alpha-parts in it (results might vary depending on the alpha-package).If you are using an alpha package, your package must be beta or lower, if you are exposing the API of the alpha package (by extending the class), your package must also be alpha.