Re: Current Directory structure ?

[Bertrand Mansion <bmansion@mamasam.com>] > 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. > > I would also like to know why there is no HTML directory in /PEAR. Should I > create one or can someone transfer the existing one to the new one ? > > 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. > > Thanks for your replies. > > Bertrand Mansion > Mamasam I understand that a lot of people get confused by this. :-) Right now you are thinking of PEAR from the user's angle, with a simple file hierarchy containing everything. From the developers' point of view it's a bit different. PEAR has to scale in terms of the number of developers, so for practical reasons we organize the "pear" CVS module into sub-projects (packages). Each package has its own development team, release cycle and also its own directory under "pear". To take your example, a "Net" package would probably become very big and hard to maintain. So if nobody has enough interest in everything network-related to maintain a single package for "Net", smaller packages such as Net_NNTP and Net_Ping start showing up. - Stig -- Stig Sæther Bakken <ssb@alltheweb.com> Fast Search & Transfer ASA, Trondheim, Norway