Re: Re: [ANNOUNCEMENT] HTML_CSS-1.0.0RC1 (beta) Released.
| From: | Greg Beaver | Date: | Tue, 26 Jul 2005 19:16:58 +0000 |
| Subject: | Re: Re: [ANNOUNCEMENT] HTML_CSS-1.0.0RC1 (beta) Released. | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-38914@lists.php.net to get a copy of this message | ||
Klaus Guenther wrote:
On 7/26/2005 8:34 PM, Greg Beaver spake the following words:Klaus, you should know me better by now! ;) There will be absolutely no BC break. Here is the magic involved in that ensures there is no BC break: 1) users upgrading from PEAR 1.3.x or older will install using package.xml. PEAR/ErrorStack.php is actually in the PEAR 1.4.0a13 archive(!), and is in the package.xml 1.0 2) the package.xml 2.0 contains this little magic in the phprelease tag: <phprelease> <blahblahblah...> <filelist> <ignore name="PEAR/ErrorStack.php"/> </filelist> </phprelease> ensuring no conflicts with the PEAR_ErrorStack package. 3) the package.xml contains this little magic in the dependencies tag: <dependencies> <blahblahblah...> <subpackage> <name>PEAR_ErrorStack</name> <channel>pear.php.net</channel> <min>0.8.0</min> <recommended>0.8.0</recommended> </subpackage> </dependencies> This ensures that the PEAR/ErrorStack.php will not conflict with the existing installed PEAR/ErrorStack.php from PEAR 1.4.0a1 through PEAR 1.4.0a12. I have tested this on my machine, and the upgrade works perfectly. In other words. One does not need a dep on PEAR_ErrorStack to get PEAR_ErrorStack. It is still fully bundled with PEAR, a dependency on PEAR is enough to guarantee installation of PEAR_ErrorStack. However, it now also means that one can avoid dragging along the rest of PEAR and simply depend on PEAR_ErrorStack. It also means PEAR_ErrorStack is freed from PEAR's release cycle and stability marking. GregLukas Smith wrote:Hmm... about ErrorStack. I remember it being a wonderful error handling system and I'm going to implement it fully in HTML_Page2, which will be up for a release pretty soon. I'm not sure why Laurent felt it so important to change the error handling except perhaps that ErrorStack wasn't and therefore it would prevent any package using it from going stable. Now that it's being split out of the main PEAR install, could you explain how that's going to maintain BC? The way I understand it, all packages using ErrorStack will need to add a dependency. And if someone upgrades PEAR without installing ErrorStack, too, that will be problematic. Or am I missing something here?PEAR Announce wrote:Yep. Unfortunately, it appears to be too much effort for some developers.- PEAR_ErrorStack was replaced by a simple way to plug in any error handling system you might want (default used PEAR_Error object)could you elaborate on this? wasnt this the original purpose of ErrorStack?