Re: pear installer in PHP 5.1 RC1

On 8/15/05, Pierre-Alain Joye <pierre@dotgeek.org> wrote: > Hello, > > Greg, again you are a very good advocate (regarding the amount of > text you can write on so simle topic). But you sadly missed the > point. This topic was debated long ago. Again, I urge you to look for and *READ* the previous thread on breaking out PEAR_ErrorStack. *ALL* issues have been thought about and taken care of. Greg even spent extra time coding to make it work. He even explained it to you in his message. Did you not read it?? > > It's about three things: > > - do not dependency if it is not absolutely required (1 file is not > what I can call absolutelly required) 1 file which is a useful package all on its own. PEAR_ErrorStack really has nothing to do especially with the PEAR package. It's its own thing, its own error handling system, PEAR_Error was pretty tightly tied to PEAR. PEAR_ErrorStack is not. > > > - PEAR_ErrorStack is somehow a PEAR_Error successor, why should it > be outside PEAR, it should not. It's sort of a successor but not entirely. Part of the reason it's not is because people haven't accepted it as a good solution. Another reason it's not used (and a few packages have even *invented* the same solution over again) is because it's part of PEAR core and not its own package. It's all about the illusion of bloat that people see. > > - BC, there is BC problems about the dependecies check, about which > package is required for an app if it uses errorstack (keeping in > mind that one may not use the installer to determine wich package > to deliver with his apps) If you had taken the time to read an understand Greg's e-mail you wouldn't say this. Please stop spreading FUD and try actually looking at the code. ErrorStack.php *will* be in the PEAR package. For PEAR < 1.4.0 it will be installed as it is now. For PEAR > 1.4.0 it won't be installed but the subpackage dependency for PEAR_ErrorStack will take effect and the file will still be installed. This is the short version. If you still don't understand it, please sit down with a cup of coffee, and review the peackage.xml files and code for PEAR 1.4.0. Run some tests. Then come back with some evidence, if you can find any. -- Justin Patrin