Slashdot Mirror

← Back to Stories (view on slashdot.org)

CVS Server Administration Tips?

Posted by Cliff on from the care-and-feeding-of-source-repositories dept.

Twintop asks: "The company I'm working for has asked me to take over administration of their CVS server for a decent sized project. The current setup of the CVS server needs to be wiped clean and started fresh. The only times I've ever used CVS (and used it poorly at that) was with a few SourceForge.net (An OSTG Site) projects. What are some suggestions on reference materials for a newbie to CVS (but not to Linux) and methods of administration that have worked for you in the past?"

3 of 79 comments (clear)

  1. Switch to SVN... by eWarz · · Score: 0, Redundant

    1) Switch to SVN

  2. SVN... by M1FCJ · · Score: 0, Redundant

    awww, I'm sticking my neck here, it can't be said enough times: switch to SVN.

  3. Re:The BEST CVS administration method by mshiltonj · · Score: 1, Redundant

    If you have an opportunity to, chuck it and use Subversion instead..

    Seconded. From a development standpoint, it takes a couple days to get used to the new way of doing things (revision # tracking is project-based, not file-based; branches and tags are really the same thing), but the features it offers (directory tracking, file moving, etc) are worth the switch!

    --
    Software Wars