Re: Re: why bloated packages are bad (acaseforsplittingup large packages)

Tobias Schlitt wrote:

I guess the question really is if the PEAR releases are really going to be so infrequent that we in the end have to make releases just for the bundled code. I just clicked through the last changelogs and I did not find a single release we did just for adding features to the core system. Usually the fixes, additions for the installer part drastically outweight the changes to other components.

If I get you right you say, that the installer only had to be released because of breaks in other packages?

No, the other way around. All the recent PEAR releases had to do with bugs in the installer code and not in PEAR.php, PEAR_Error .. not even for the development steps of ErrorStack. Then again I dont know if updates where delayed due to waiting for the next PEAR release. However in the few versions I clicked through the number of installer related fixed clearly outweight the number of fixes to other infrastructure code. So I am wondering if we will really "safe" all that many PEAR releases by undbundling ErrorStack which should probably get less likely to be changed now that its approach stable state. regards, Lukas