Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

macOS Source Code Version System recommendation

macridah

macridah

macrumors 6502a
Original poster
Feb 18, 2004
868
0
Nor-Cal
Hi all,

Any recommendations for a version control system to install on the mac os x server?

Thanks in advance.
 
If you're interested in a commercial solution, take a look at Perforce http://www.perforce.com/. There are clients for most major operating systems.

It's pricey for multiple users but if this is for your personal use, you can (see their site for the limitations on number of users and workspaces) install and use it for free.
 
macridah said:
Hi all,

Any recommendations for a version control system to install on the mac os x server?

Thanks in advance.
Click to expand...

Perforce (at www.perforce.com) is the absolute best.

Free version supports two users and five workspaces.

Unlimited free version is available for open source projects (very simple rule: You have to give perforce read access to everything checked in...)

Unlimited commercial version available at reasonable prices. Supports hundreds of users easily.
 
cvs is the standard, but most projects I know of are starting to transition to subversion. If you want to pay for bells&whistles Perforce is apparently the way to go.

If it was my call, and occasionally it is, I'd be running subversion.
 
Westside guy said:
Speaking from the user point of view, I've yet to see what real advantages Subversion offers over CVS. I'd say if you're more familiar with one versus the other, then go with that.
Click to expand...

I'm stunned to read this. When Adium switched from CVS to SVN it was an enormous improvement. Offline diffs (so I can make patches while traveling), transactions (so the repository is always in a consistent state), cheap branches (svn branches are copy-on-write, so O(1) to create), and per-commit revision numbers are all huge advantages. Integration with Trac is nice as well.
 
Catfish_Man said:
I'm stunned to read this. When Adium switched from CVS to SVN it was an enormous improvement. Offline diffs (so I can make patches while traveling), transactions (so the repository is always in a consistent state), cheap branches (svn branches are copy-on-write, so O(1) to create), and per-commit revision numbers are all huge advantages. Integration with Trac is nice as well.
Click to expand...

Sorry to have "stunned" you. :D But you seem to be speaking largely from the standpoint of someone with commit access, while I (as I said right up front) was speaking from the end user point of view. But I guess macridah has to consider what he/she plans to do with the repository:

- is it just for personal use or for a small group only? if so, do any of the stated svn improvements matter from a practical point of view? (of course in this case I also have to point out that my "end user" point of view is pretty much irrelevant, since everyone will be maintaining code)

- how much time does he/she want to put into maintaining the system? CVS is built in with OS X, while SVN will have to be separately installed and maintained (not necessarily difficult, but definitely necessary). SVN does have the reputation for being more time-consuming for the admin.

- Conversely, if this is just for personal use (or for a small group) then it doesn't matter as much if it takes more time to set up and manage SVN vs CVS.
 
Westside guy said:
Sorry to have "stunned" you. :D But you seem to be speaking largely from the standpoint of someone with commit access, while I (as I said right up front) was speaking from the end user point of view.
Click to expand...


Ah, I figured "end user" meant developer rather than admin. Yeah, for read-only access or no access, it's the same as CVS basically.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back