Existing users, log in.  New users, create a free account.  Lost password?

Mac OS X  |  IT & Network Administration  |  Other Network / Admin  |  Perforce  |  Hard to use, very expensive, and very "closed"

Perforce

Perforce

Version control system uses SCM protocol.

Version:  2009.1

   [ Views: 873 ]

Hard to use, very expensive, and very "closed"

Feedback Type:  Review

Contributed by: dylan3--2008 Thursday, September 09 2004 @ 12:28 PM PDT

Product Platform: MacOSX

Used Product For: Less than a month

Recommend Product: NO

A few months ago, I was looking for something better than CVS. I heard good things about it, so I tried Perforce. I'm an experienced Unix guy, but I had a hard time installing it. After installing it, I had a hard time using it. (I'm used to CVS, so I thought I was used to hard-to-use version control systems). Finally, after giving up, I found it hard to extract my life out of Perforce.

Then I heard about Subversion. In contrast to Perforce, Subversion was easier to install (though not easy yet), and MUCH easier to use. Plus, it's free! http://subversion.tigris.org/   
Overall Rating:

Ease of Use:

Support:

Features:

Quality / Stability:

Price:

Rate this Review

Was this Review helpful? Yes | No

Comments

2 comments |

Hard to use, very expensive, and very "closed" - pfworks

The real place that perforce shines is that once you have several dozen development and release branches, you can easily integrate changes and know exactly what is where, even if developers make cryptic, one word checkin comments.

We recently switched from Subversion to Perforce. I can't imagine managing releases with subversion.

Coupled with parabuild (http://www.viewtier.com) and bugzilla, you have a complete bug, release, source control and CI solution.

Reply to This

Friday, June 20 2008 @ 09:27 PM PDT


Hard to use, very expensive, and very "closed" - justwhatever

I'm not sure what you found difficult about setting up the server, as it consists of a single unix 'server' tool, that works quite easily with launchd on Mac OS X. There are some parameters to specify when running the tool, but the pdf manual pretty clearly explains them (basically, put scm revision files inside folder at path X, and put scm incremental files at path Y (which should be on a different physical HD). The client configuration/usage can take a bit of time to sort out, but getting the server going was easy, as it behaves very much like many other unix daemons.

Reply to This

Tuesday, August 18 2009 @ 11:26 PM PDT