Slashdot Mirror

← Back to Stories (view on slashdot.org)

Version Control with CVS on Mac OS X

Posted by pudge on from the version-controlling-goodness dept.

Ryan writes "Apple recently published an article on using CVS with Mac OS X. 'This article covers some of the most commonly used features of CVS, with emphasis on using CVS with static and interpreted web files (HTML, PHP, Perl, etc).'" It's a decent article, a good primer on how to get started, and it's nice that Mac OS X comes with a CVS server. Personally, I really dig maccvs for my CVS client, and there are plenty of other clients for Mac OS out there too.

4 of 20 comments (clear)

  1. Default version is 1.10 by Channing · · Score: 4, Informative

    By default, cvs version 1.10 is installed which caused me some problems when connecting from a remote client to a repository on OSX.

    It was easy to build the latest version but I hope Apple updates the default soon.

    Chang

  2. Re:Project Builder Integration by tb3 · · Score: 5, Informative

    There's a decent article on CocoaDevCentral about setting up CVS and ProjectBuilder.

    I managed to get it working without too much trouble. It works pretty much the way you'd expect an IDE to work with SCM.

    --

    www.lucernesys.comHorizon: Calendar-based personal finance

  3. Re:very interesting by dborod · · Score: 3, Informative

    i had to compile and install it myself, and then...

    You can grab a bash binary at:

    http://www.osxgnu.org/software/Shells/bash/

    The package installs nicely and includes directions on how to have it become your default shell.

    If I had a sig you'd be done reading it

  4. Re:maccvs works? by Clith · · Score: 2, Informative
    I do commercial Mac software development, and we use MacCVS Pro to great effect. I recommend it highly. It doesn't hurt that it's GPL and has been stable for over a year.

    It is interesting to note that the new version of CodeWarrior for MacOS, version 8, comes with a CVS plugin (not mentioned on that page). I haven't had a chance to try it yet, though.

    One thing that does bother me about the various incarnations of CVS on the Mac is how poorly they work together. Partly this is because of the different ways in which they work around CVS' inability to deal with MacOS' multi-forked files. For cocoa apps [like iJournal and Fire] this is not much of a problem, because the old NeXT-style Cocoa development environment sticks strictly to simple data files with no resource forks, which works perfectly with all varieties of CVS.

    The upshot is that if you are working with files with resource forks using CVS, you'd better make sure everyone agrees which CVS client you are going to use.

    --
    [ReidNews]