I also really liked how the hierarchical view automatically refreshed to reflect the most recent changes to the sandbox area and files within the sandbox. It works well with my CVS repositories and I like the concept of opening a sandbox to get a hierarchical view of the files. Now this product is more to my liking especially after looking at the other options. The next CVS client I looked at was MacCVSClient version 1.10. According to the release notes in the readme file the latest build of MacCVS Pro “will only run on PPC machines (and Intel machines via Rosetta).” And the readme goes on to say “This is likely the last version that will be built using CodeWarrior, since CodeWarrior is no longer commercially available.” So MacCVS Pro is not the CVS client for me. The latest update at the time of this writing is January 14, 2007. ![]() The up-to-date MacCVS Pro can be found at. I doubt it will run on my Intel-based MacBook Pro so I didn’t bother to download it.Īfter more searching I discovered that the MacCVS Pro website at is out of date and no longer maintained, but the project lives on at. The revision history shows the last update to be March 27, 2000. I looked at MacCVS Pro next, but I never downloaded it. Thus my search for a CVS client for Mac OS X continued. While I can do everything I need to using MacCvsX, I found it UI to be inefficient. There is no “Add Content” feature like that found in TortoiseCVS. Also, I didn’t like the fact that when I wanted to add lots of new files to the repository I had to select each and every file individually. This client has no problems accessing my CVS repositories but I found the UI to be a bit cumbersome. The next CVS client I tried was MacCvsX (version 3.3 beta 2). So even if Xcode did work with CVSNT and I was able to use sserver, I still could not use Xcode as my CVS client. I tried this 3 times and the crash happened all 3 times. I was testing with a rather large repository and the crash happened after about 20 minutes of download time. Secondly, when I was finally able to get Xcode to checkout a complete repository it would crash Xcode. For starters, there is no way (that I can find) for specifying a module. Unfortunately Xcode has a problem with sending the password to CVSNT and since CVS doesn’t support sserver Xcode was quickly off my list of CVS clients to consider.įor grins I decided to enable pserver on one of my CVS repositories to test Xcode with CVS. The workaround for this is to use CVSNT instead of CVS, which comes installed by default on OS X. The first problem I encountered was the lack of sserver support. I like the approach used in Xcode but I wasn’t able to get it working with my CVS repositories. Xcode from Apple has an SCM repository feature that works with CVS, Subversion, and Perforce. That’s what I went searching for and here is what I found: My preference for a CVS client for the Mac would be one that provides a Finder like user interface and uses right-click popup menus to interact with the CVS repository. ![]() The CVS client I use needs to be as good as, or close to, TortoiseCVS. ![]() This of course is what I used as a baseline for finding a CVS client for the Mac. TortoiseCVS is the CVS client I use on Windows and is by far, in my opinion, the best Windows CVS client out there. This blog post is about my review of the various CVS clients available for Mac OS X. If I were starting from scratch I would most likely select Subversion for versioning control, but that’s a different story for a different blog post. It works for me and I see no reason for moving to Subversion. The use of version control software is part of the software methodology used at White Peak Software, and the version control software I used is CVS (Concurrent Versioning System). I’ve been a Mac user for a little more than 6 months now, and while I’m still writing software for the Windows platform, I’m toying with the idea of targeting OS X for an upcoming product.
0 Comments
Leave a Reply. |