Re: future of PEAR (was [PEAR-DEV] [Call For

On 11 Nov 2003 at 20:09, Tobias Schlitt wrote: > On Tue, 2003-11-11 at 05:49, Greg Beaver wrote: > > > > Issues concerning subpackaging should IMHO discussed, too. > > > I wrote an rfc regarding subpackages that received quite literally > > no discussion whatsoever :). It is now sitting in the > > php-src/pear/docs directory of CVS if you would like to review it. > > I have every intention of coding subpackages for PEAR 1.4, as I've > > written several incarnations for earlier PEAR versions, and the only > > extensive code will actually need to be at pear.php.net rather than > > in the installer. > > I really like the approach. Another well thought idea, IMHO. But I'm > shure, that this would be cleaner with a PEAR2 approach, because we > can integrate subpackes cleaner in CVS by doing sth like: > > <snip> > pear/ > Categorie/ > Package/ > Package.php > Subpackage/ > Subpackage.php > </snip> > > This directory structure looks much cleaner in my oppinion and could > be matched to users PEAR directories, as well as to CVS structure > (which would definitly raise developement comfort very much). Well, you don't need to branch of a PEAR2 for streamlining the layout of CVS. I think if there are certain rules we could find some weekend on which CVS will not be used by anyone (for writing) and on which some persons on the server could "by hand" change things like the directory-structure of existing packages etc. If you don't want to loose all CVS-changelogs (and since this is unfortunately not a Subversion-server :-((() this is the only way to rename / move files - "the hard way". And yes, I would appreciate a discussion about directory structures and filenames for CVS and for the packets. Some while ago somebody mentioned "doc" and "docs" being directories of packages, or having "examples" and "samples" and things like that. Also I would like to know if e.g. the main file of the Image_Graph- package should go into: Image/Graph.php (as it is now - which is good in my oppinion) or use Image/Image_Graph.php (which is what Image_Text.php currently does afaik or if we should use some name with PEAR_ included in the filename (as Greg proposed - or was he just talking about class names?). Regards, Stefan