Re: Re: CVS Access Method

<no quote because this is really just a reply to the whole thread> I'm just catching up on my PEAR e-mail now after a big weekend, but I'm +1 on SVN for very large values of 1. We use it here at work, and having to go back to CVS after using SVN is really quite painful -- things like atomic commits, directory versioning and branch/tag semantics that make sense to me (which I'm aware puts me at odds with numerous other PEAR developers who are more comfortable with CVS) are just too good to give up willingly. Of course, if we switch to SVN we could then use Trac as well, but I don't know that it would look especially good for a PHP project to be using Python-based software. :) As for distributed systems, I'm not sure that they actually make sense for a lot of PEAR's packages. So many of our packages have only one or two developers that using distributed source control might not be much of a win anyway, and it's nice to be able to point people at "one true repository" for a package. Adam -- Adam Harvey PEAR Profile: <http://pear.php.net/user/aharvey> Blog: <http://xn--9bi.net/>