Re: [RFC] CVS directory structure

Hi! Tobias Schlitt wrote:

Issues: => reduces patch creation by foreigners => reduces tests by foreigners => scare potential developement

Any hard facts to back these up? For me it looks like FUD.

Solution -------- To solve this issue, one of the following solutions should be (optional?) used for a packages CVS directory. 1. Change the PEAR CVS directory structure to reflect the PEAR user directory structure completly. Simply use ini_set('include_path', '/your/cvs/pear'); or any other mechanism to require PEAR directories. 2. Change the PEAR CVS directory structur to reflect parts of the PEAR user directory structure. Insert a directory level into every package directory which is named after the category and store all package needed files below this.

Solution 1. is obviosly unacceptable (PEAR CVS has this structure a long time ago and it was changed to the current one for a reason that is decribed in the docs). Solution 2. may be acceptable, but as there are dozens of PEAR developers who are comfortable with the current structure and only few who complain, I don't see a point in forcing it. As Martin Jansen pointed out, you are not required to use the PEAR CVS repository, you can use your own one and have any structure you like there. -1 from me.