Re: Current Directory structure ?

From: Date: Thu, 09 Aug 2001 11:59:46 +0000
Subject: Re: Current Directory structure ?
References: 1  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-1337@lists.php.net to get a copy of this message
[Bertrand Mansion <bmansion@mamasam.com>] > le 8/08/01 23:34, Christian Stocker à chregu@phant.ch a écrit : > > >> 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. > > OK I didn't know. I think it just adds some confusion to the organisation, > but I will probably get used to it. Then, maybe it is time to do the same > thing for Crypt directory and the others. I don't understand how you will > manage packages like HTTP for example. HTTP_HTTP/ ? or just HTTP/ ? and if > there is a http_compress class where will it go ? in HTTP/HTTP_Compress/ or > just HTTP/? What was clear before is now confusing. Each package has its directory directly under "pear". The directory name is the same as the package name, and you could say they are both based on the name of your main class. So if you're starting a separate package/project where everything is in a class called "HTTP_Compress", that's your package (and directory) name. If you have a hierarchy of classes like in DB (DB, DB_result, DB_mysql, DB_storage etc), you name your class after the "root" class. Still confused? Not after this week's episode of... pears in space! > Are all the packages in pear directory classified this way or only a > part of them ? Maybe it is time to start on a good directory > structure before people start to add new extensions. > > >> 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. > > Don't you have a more precise date? At what times the cron task will > happen? Where can I find this global package.xml file ? It is not > urgent but I would be glad to know. Don't worry about a global packages file for now. Hopefully we'll have the web site up in a month or so, things should become much clearer by then. - Stig -- Stig Sæther Bakken <ssb@alltheweb.com> Fast Search & Transfer ASA, Trondheim, Norway

« previous php.pear.dev (#1337) next »