Re: Re: CVS Access Method
| From: | Jan Schneider | Date: | Wed, 07 Feb 2007 09:19:53 +0000 |
| Subject: | Re: Re: CVS Access Method | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-45614@lists.php.net to get a copy of this message | ||
Zitat von Gregory Beaver <greg@chiaraquartet.net>:
Bertrand Mansion wrote:Why would you want to do that anyway? Jan. -- Do you need professional PHP or Horde consulting? http://horde.org/consulting/This is probably a project for 2008 anyway :) On the other hand, I don't see what Subversion could really bring to PEAR, even when I read http://oss.backendmedia.com/PHPSVN/ most of the points I see are wrong or useless, except being able to move directories maybe. PEAR is really different from other projects like Mozilla or even PHP itself, which are compact. I wonder if it wouldn't be better to setup one repository per project/package instead of one repository for everything in PEAR ? Using a distributed system, it would be very easy to manage. If PEAR were a framework, it would make sense to have only one repository. But packages are not tied together and that's the idea of PEAR. Then why would they share the same changesets and revision numbers. Furthermore, with multiple repository, it becomes easier to manage partial checkouts, permissions, workload, bandwidth, etc :) That's just an idea.Hi, This actually sounds reasonable to me as an idea. It would greatly simplify checking out, and ease bandwidth issues in some cases. However, it would make it more difficult to check out the entire PEAR project, wouldn't it?