Re: standards etc..

"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. > > > (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.) > > For the moment we haven't yet in mind stablish any relation between CVS > and the Pear package distribution web system. People will upload to the > web pre-built packages made with the "pear package" command. > > > > 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. > > > > If you have a recent version of PHP (guess >= 4.0.5) try to launch the > "pear" command at your command prompt. Yeah this is the > builder/installer of pear packages. > > For real working example, try: > # pear install > http://vulcanonet.com/soft/upload/HTTP_Uploader-0.6.4.tgz > > (notes: will only work with the CVS version of the pear script and > PEAR/* classes, and only under *nix). cool. will give that a go later on :o) > > > Tomas V.V.Cox / d