Speaking for myself only, of course: Please, for the love of god, move away 
from CVS. Moving the code to a more modern VCS and a well-supported host. The 
least-painful move might be to SVN on Google Code.

I'm pretty sure there's nothing but CVS available for OS9, though, so the 
question has to be whether or not the pain of using CVS on Sourceforge 
outweighs the potential loss of people stuck on ancient OS's. With apologies to 
Bryan, I know I'd be a lot more likely to work with the code if it were hosted 
in a way that made it easier for me to deal with.

 -Bill-


On 7/22/09 8:23 PM, "Bryan Baldus" <bryan.bal...@quality-books.com> wrote:

On Wednesday, July 22, 2009 4:10 PM, Galen Charlton 
[galen.charl...@liblime.com] wrote:
>Funny you should mention CVS.  I have a general question for the
MARC/Perl hackers: Ed mentioned a while back moving from CVS to a more
modern VCS such as Subversion or (my preference) Git.  I'm willing to
do the legwork to get the repositories moved.  Thoughts?<

Speaking as a hobbyist programmer, I've only used CVS, and would hope that a 
move to a different system wouldn't make it a more complicated or difficult to 
use system. Until last November, my main development machine was (and still 
would be) a PowerMac 7500/G3 with MacOS 9. When I tried to update SourceForge 
CVS this May using my Mac, I believe my SSH login failed (it had worked fine in 
August 2008), so I switched to updating SourceForge CVS using WinCvs on my 
Windows Vista laptop (Nov. 2008). I'm not sure what changed to prevent the Mac 
from being able to get a SSH connection to SourceForge, but I chalked it up to 
being an age thing (SourceForge update making old operating systems obsolete; 
or some change to SSH that I couldn't figure out how to fix in the MacSSH 
client; it does seem like it took a little bit of work getting WinCvs set up, 
as well), and that from now on, the Windows machine will be what I need to use 
to be able to update anything on SourceForge. So, as long as there is an 
easy-to-use Windows-based client for the other version control systems, then I 
probably wouldn't have a problem with switching.

Thank you for your time,

Bryan Baldus
bryan.bal...@quality-books.com
eij...@cpan.org
http://home.inwave.com/eija

Reply via email to