CVS or Subversion

[Unheard]

I'm looking to implement version control @ my office, and was wanting to know which software package I should go with, pro's and cons of each, and ease of setup.

Also does anyone know of a prepackage Linux setup that is designed for strictly source control?

Thanks!

 

[Drakkon]

Depends on what your programming in and versioning I've found. SVN overall has been better to implement for what i do (flash, php) as it can handle other files such as graphics and fla files while CVS has some trouble.

As for prepackaged theres not much out there however personally I've found it nicer on a windows box to administrate cause you can use domain logins to handle accounts and administrative interface panels are available that make it all easier to navigate and understand when setting up.

I'd say setup an account on http://cvsdude.com/product.pl and see what its like before commiting either way to make sure the file types you want to deal with are going to be accepted

 

[mundane]

We are slowly transitioning from SVS to SVN. Our server is Linux (SUSE, but *any* Linux distro should have it packaged), and we have Subversion configured to run under https. I find it easy to maintain, and I can accomplish any admin task through SSH.

 

[Nothinman]

Subversion was designed to be a better CVS so I don't think there's really any reason to choose CVS over SVN unless you've already got a vested interest in CVS. But a good place to start would probably be the book they have online, read through it a bit to see what you're getting yourself into before committing, no pun intended. =)

http://svnbook.red-bean.com/