Re: Re: why bloated packages are bad (a case forsplitting up large packages)

Lukas Smith <lsmith@php.net> > Clay you are getting quite worked up here. Yes, I am. > I was saying that Greg is mixing issues. If he needs to solve an issue > regarding optional dependencies he obviously needs to look at optional > dependencies. But this does not mean that every single unit test needs > to bother optional unit tests and as such Greg was mixing issues when he > took the issue of ErrorStack and mixed it with the fact that he is > debugging an issue with optional depdencies. No, Greg's issue was in regard to bloat, and the number of implicit dependencies that bloated code requires. He said: > Developers wishing to use PEAR_ErrorStack at present have implicit > dependencies on Archive_Tar and Console_Getopt because PEAR requires them, > even though they have nothing to do with PEAR_ErrorStack. He then used the issues surrounding bug #5085 _as an example of_ the bloat. If you're not following the connection, I think you need to re-read Greg's original email slowly. > Finally argueing that Pierre does not know the pear installer (1.3 or > 1.4) is stretching your argument well within the reach of personal > insult. If Pierre, or anyone else involved in decisions regarding PEAR-CORE, takes personal offense at my opinion that developers who don't know the current code shouldn't be involved in the decision making process, so be it. Pierre's been illustrating (and admitting!) that he isn't familiar with the PEAR 1.4.0 code in this discussion. There's nothing personal here -- it's just common sense that the decision-making body actually BE familiar with what they're attempting to make decisions about. The PEAR community expects, and deserves, this simple requirement. -Clay -- Killersoft.com