Re: standards etc..

Daniel Andersson <daniel@avantnoise.com> wrote: > hum. okay, i can see this point. > > BUT, won't most of the HTML_* be dependent on HTML or? > > and if, then you still can't do minor releases but have to wait for HTML or > HTML_* to finish. the basic problem is that with the more code you have in a pile that is released as one big package, the harder it is to stabilize all the pieces and actually release something. (witness the painful process of actually doing a php release. there's a reason there's only been six releases in over a year. :) the best way to handle this problem, that i've seen, is a packaging system with rich conflict and dependency checking, a la dpkg. or cpan. seperating HTML from HTML_Table and HTML_Form in the cvs repository is just a way of making the package boundaries clear. some packages may include some of their subclasses, in which case they would be located where you might expect. (one thing to keep in mind is that not all packages distributed from pear.php.net will necessarily be in the pear cvs tree. it will be possible to directly upload package releases. the pear cvs tree is just a form of free cvs hosting, really.) > and even if you had it HTML/Form you could still do small updates/releases. > > just adding a small installer of some sort that will install the package > into the right directory :o) that is part of what is being built. jim