Re: Current Directory structure ?

["Tomas V.V.Cox" <cox@idecnet.com>] > Stig Sæther Bakken wrote: > > > > [Christian Stocker <chregu@phant.ch>] > > > Hi > > > > > > > I have looked at the current PEAR directory structure in the CVS > > > > tree and I don't understand why there are so many Net_... and > > > > XML_... directories. Shouldn't these directories be under Net/ > > > > and XML/ ? This is unclear to me. > > > > > > this was discussed some time ago and it was decided, that each > > > package has it's own dir on the top level. > > > > > > > And finally, are we going to have a global XML file with details > > > > on all PEAR extensions (a bit like package.xml) ? It would be > > > > easier to create installer client applications and to get details > > > > directly from them. > > > > > > the script /pearweb/cron/make-packages.php creates .tgz files of all > > > packages plus a xml-file (Packages.xml) with some relevant > > > information about these packages. the WebInstaller uses already this > > > xml file. the make-packages.php will run on pear.php.net in the > > > (hopefully) near future. > > > > Btw, there is a problem with the make-packages script as long as > > there are no CVS tags in any modules. The code you check out the next > > day may give you a package with the same version number but different > > files. > > > > I guess this last should be done by a shell script in cron, that finally > calls the make-packages. Or you are thinking in doing this directly from > php like chora? Two options: a script like make-packages.php, or generating the tarballs on the fly as long as they are CVS-hosted at cvs.php.net. But that'd only be for bootstrapping really, in the future when people do releases through the web interface, the tarball will either be uploaded as part of the release, or generated from a CVS release checkout. - Stig -- Stig Sæther Bakken <ssb@alltheweb.com> Fast Search & Transfer ASA, Trondheim, Norway