Comparison between Perforce

Back to main page

SCM feature:	Perforce	Add to comparison: +CVS +AccuRev +Aegis +AllChange +Arch +Bazaar +BitKeeper +ClearCase +CM+ +CMSynergy +Co-Op +Darcs +Git +LibreSource Synchronizer +Mercurial +Monotone +OpenCM +PureCM +SourceAnywhere +Subversion +Superversion +Surround SCM +svk +Team Foundation Server +Vesta +Visual SourceSafe
Atomic Commits	Yes. Commits are atomic.
Files and Directories Moves or Renames	Not directly (you copy and then delete but it manages to keep track of the branch)
Intelligent Merging after Moves or Renames	Partial. While perforce doesn't explicitly support renames (one hsa to do a copy+delete), it does keep track of the full revision and integration history across copying, so changing a file in the copied directory and trying to merge it does the right thing.
File and Directories Copies	Copies are supported (though, because of its architecture, I don't know how well)
Remote Repository Replication	Yes. Via the Perforce Proxy (P4P) tool.
Propagating Changes to Parent Repositories	Unknown. Probably Not.
Repository Permissions	Yes. (more than half a dozen of permission levels that can be set in a file by file basis)
Changesets' Support	Yes. Changesets are supported.
Tracking Line-wise File History	Yes, an annotation feature is present.
Ability to Work only on One Directory of the Repository	Yes. Changes to a sub-directory of the repository are supported.
Tracking Uncommited Changes	Yes.
Per-File Commit Messages	No. Commit messages are per change.
Documentation	Very Good (html and command line help)
Ease of Deployment	Very good. Perforce is very easy to deploy.
Command Set	Very extensive but not compatible with CVS.
Networking Support	Good. (single TCP/IP socket)
Portability	Excellent. Runs on UNIX, Mac OS, BeOS and Windows.
Web Interface	Yes, P4Web.
Availability of Graphical User-Interfaces.	Yes, P4Win and others based on the available libp4 library.