Re: standards etc..

["Daniel Andersson" <daniel@avantnoise.com>] > "Tomas V.V.Cox" <cox@idecnet.com> wrote in message > news:3B85B0FF.20DE6590@idecnet.com... > > (only some extra notes from me) > > > > jimw@apache.org wrote: > > > > > > 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. > > > > Also many Pear packages are distributed as independant components. For > > example you could just download Mail_mime or Net_NNTP without the need > > of all Mail or Net packages. > > hum. yes, i can see this. but by locating it somewhere else Net/NTTP instead > of Net_NTTP wouldn't stop that, would it? > > i can see the thing about it being hard thing about stabilize something > quite big, but on the other hand i can't see the use of another directory > structure stopping that. Pratical reasons. There is a whole bunch of things that get really messy if you mix several packages in the same tree. There's more on this in the archive. - Stig -- Stig Sæther Bakken <ssb@alltheweb.com> Fast Search & Transfer ASA, Trondheim, Norway