Re: Re: CVS Access Method

Bertrand Mansion wrote: > 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? As for Anant's idea of encouraging people to use repositories outside of pear.php.net, this is not a good idea if we want to encourage people to congregate at pear.php.net. If PEAR2 will simply be an installer that links together several other sites, i.e. a channel aggregator, then I think we should encourage decentralization. However, this decision has not even been hinted at yet, so I would say "no way" to encouraging decentralization of the PEAR repository. One real benefit of using a decentralized VCS is that a project could host their stuff on a remote server, and pear.php.net could be set up simply to synchronize using a cron job, providing a centralization even if the user never pushes their stuff to pear.php.net directly. In this way, we could support a decentralized approach AND a centralized approach. One question: CVS allows creating "fake" repositories with symlinks (i.e. some pecl packages are symlinked directly into php-src/ext), have you found a way to do this with Mercurial or other decentralized approaches? Greg