Setting up a CVS server on Mac OSX in 4 steps and 4 minutes

Posted 1 year, 10 months ago at 5:50 pm. 8 comments

So. I wanted to set up a cvs server under OSX. I looked around and found a few people with docs about how to set up xinetd or set up launchd, blah blah blah, but I didn’t want to deal with that. Yeah, I know OSX is unix and isn’t that great, but I want something like the old days where to install a web server, you just launched the MacHTTP app and you were done. No config files, just simple apps. Want a mail server? Fire up EIMS. Ah, the good old days…

So, as it turns out, it apparently _is_ simple to get cvs working under OSX. Here are the steps (from memory, so I might have missed something, but damn it’s simple)

  1. Insert OSX Install Disc 1 and launch the Xcode Tools / XcodeTools.mpkg installer, Continue, Continue, Agree, Continue, Customize, deselect everything except for the top item, “Developer Tools Software”. Finish the install
  2. Fire up Terminal and make a cvs-repository directory in your home directory (or wherever, but that’s what I used): “mkdir cvs-repository”
  3. Add required files to the cvs repository with “cvs -d /Users/erich/cvs-repository init”
  4. Open your System Preferences, Sharing, Services - make sure Remote Login is enabled
  5. There is no step 5

That’s it. I fired up Eclipse, made a test project, connected using the IP address (not by name, for simplicity) of the OSX box, connection type of “extssh”, repository path of “/Users/erich/cvs-repository”, and it worked. That was it.

Secure cvs, no pserver bullshit.

Almost back to the old days. Way better than trying to set this up on Winders. But I can dream of a CVS.app someday, right? Are you on that? :-)

8 Replies

  1. Dave Yost Nov 28th 2006

    Nice of you to give people a cookbook, but you should also print in bold letters Do not use cvs. It is obsolete. I don’t yet have personal experience with other VCS’s, but everyone says that Subversion is now better, and many I know say Subversion is obsoleted by darcs, mercurial, and others.

  2. Have to disagree with you, Dave. CVS is old, simple, stable, and fast. Subversion is shiny and new, buggy (yes, it’s bitten me several times over the past year) and slooooooooooooow. Lordy it’s slow.

    I really don’t undestand the hype that’s following svn around. If you ask people what’s good about it, they tend to focus on atomic commits, which I haven’t found to be that useful except for the promise of miraculous branching and merging. Which works about 90% of the time. That last 10% hurts bad when it fails… yowch.

    There are lots of reasons to pick one version control system over another, and I encourage everyone to decide on their own. But for a very simple and reasonably reliable version control system that can be set up in 4 minutes, whether for use by yourself solo or with other people, CVS works great on OSX.

    Have fun, everybody!

  3. CVS is not obsolete at all. Subversion is very difficult to install. It imposes its own directory structure on all your projects. Also, when people compare the features of Subversion to those of CVS, they always tend to use some ancient version of CVS. The people at March Hare have a very nice, open-source version of CVS that runs on all platforms and does everything that Subversion can.

    Erich is right. Pick your version control system based on what you like to use, not what other people are using.

    And BTW, Step #4 is optional.

  4. Thanks a lot.
    It cost me half a day of research, try&error, man pages, google etc. etc. Then I found this cookbook and voila: It’s really as simple as that :-)

    Frank

  5. Thanks!!!!

    Agreeing to Frank, I spent quite a bit of time trying to set up repository on a external drive connected to my airport extreme.
    Followed the instructions in your cookbook and it was done in a few minutes.

    Cheers, Sven

  6. Thanks for this! A couple of differences I found: 1) Xcode was on OS X Disc 2, not Disc 1 on my Leopard discs; and 2) Remote Login did have to be enabled, I did not find it to be optional as Etresoft noted.

  7. Andrew Sep 28th 2008

    THANK YOU for the instructions…. i spent 2 hours scouring the web (ie googling) (and invented a few poetic swear phrases along the way) to find instructions on how to connect eclipse with cvs on a mac os x (leopard) because i was getting connection refused errors, and found nothing that worked… until this page! and all it took was a single check of the remote login in system preferences…. cool!


Leave a Reply