php4/ vs pear/php4/

Bertrand Mansion wrote: > > >> /pear/HTML Common.php > >> Log: > >> Move from /php4/pear/HTML to /pear/HTML > >> > > > > Please do not move core classes from php4/pear/! You will break the > > compatibility with too much things. > > Well, I didn't actually moved it, I just copied it. > I thought that was what we were supposed to do. I am still confused with > what we are supposed to do, where we are supposed to put things, and so on. > pear directory is a mess. > > If only the gurus know what has to be done, well, they can probably do it > themselves then. It's not such a complicate thing, really. Only need to understand that there are two different things: 1) The directory were all the classes will be stored after the installation. 2) The directory were Pear developers works in their developments. When people installs php, all the classes under php4/pear/ will be installed in /usr/local/lib/php/. So the CVS directory php4/pear/ is the destination pear tree. In the other hand, we have the pear/ CVS module. This is only a tool that Pear offers to its contributors and developers, but has nothing to do with the install process of Pear classes. So the question now is: How can I distribute the software I commit to "pear/"? The answer is: across pear packages and the Pear web. The process more or less will be so: # cvs co pear/HTML_Quick # pear package pear/HTML_Quick/pakage.xml Now you get the pear package of your classes in a file wich will look like: HTML_Quick-1.13.tgz Then go to the web, and submit your package. Inmediatly it will be avaible to the world. We plan also, use the same "pear" script to publish the new realeases. Something like so: # pear publish user pass HTML_Quick-1.13.tgz Users of your class could install it, downloading it from the web and calling the "pear install HTML_Quick-1.13.tgz" command. Also they will be able to directly remote install packages with something like: # pear install http://pear.php.net/packages/download/XXXX We are in the way of finishing the "pear" script (yet quite functional) and the Pear web (the main working of us is on it right now). There are many other things to tell, but that's the basic idea. Tomas V.V.Cox