Perforce Software Configuration Management System
One of the particularly strong points of Perforce is the way it handles branches, called “inter-file branching”.
On many other systems the branch specification is in some way part of the version numbering or version selection mechanism. This is counter intuitive and is often a cause of confusion. Other systems also make branches of individual files.
Perforce handles branch naming in the same way that you would without a code-management system. In Perforce, the directory my_project/new_branch/ contains the new branch of my_project/old_branch. By making the branch naming a part of the directory tree structure, Perforce has created a very natural way to interact with and think about branches.
In this way a branch is simultaneously created for the complete project, not just for an individual file. This method also helps to keep the branches consistent. A copying algorithm in the server prevents this approach from using more disk space than other approaches.
Above, I have described the normal use of the Perforce branching mechanism. However, the Perforce branching mechanism is even more powerful. It is possible to specify that file trees or individual files are branches of each other. It is even possible to designate two totally unrelated files or directory trees as branches and migrate changes between them.
The specification of branches is done by a branch view. The branch view can contain a simple or arbitrarily complex mapping between file names in the two branches.
Perforce uses the powerful command p4 integ and p4 resolve to integrate changes between the branches and to resolve conflicts.
Perforce is a very fast, code-management system. Code-management actions, such as labelling, checking in (P4 submit) and checking out (p4 edit) are several magnitudes faster than ClearCase, another code-management system.
With Perforce, all normal work such as editing and compiling is done on local files in your work area, making Perforce much faster than most other systems.
Perforce has a number of advanced features. I cannot list all of them (much less describe them all) in this space, but I will mention a few.
Perforce can have distributed depots. You can run Perforce over WANs, and you can even run it encrypted over the Internet. You can use Perforce with IP-tunneling and firewalls. Perforce can have change submission triggers for external processes.
Perforce has support for off-line clients. That is, it is possible to disconnect a client computer and make changes to the local files in the workspace, and afterwards let Perforce detect the changes and bring them into the depot.
You can download all of Perforce, except the license file, from ftp://ftp.perforce.com/. The license file determines how many users the server accepts. Without a license file, there can be only 2 users. The cost of purchasing Perforce (i.e., the license file) is $500US/user. If you purchase Perforce, they e-mail the license file to you. Perforce has announced:
Non-commercial users of Free-BSD and LINUX may obtain Perforce servers supporting an unlimited number of end users gratis. This includes upgrades, but not support. Execution of a Perforce non-commercial license agreement is required.
Answering a direct question, Christopher Seiwald of Perforce, said:
We cannot guarantee non-commercial users support, but we try not to discriminate between commercial users, evaluation users and non-commercial users.
Perforce has provided excellent support to me. No matter how absurd the question or how absurd the task I am attempting, I have always received a good answer by e-mail within 18 hours. Perforce has remarkably good e-mail support. I have asked other customers of Perforce on the Net, and they have all been pleased.
I have used Perforce both professionally (see “MYDATA's Industrial Robots”, LJ Issue 39, July 1997) and as a home-hobby programmer. I find Perforce to be a good product with good support. I find other CM products that I have used professionally to be remarkably poor by comparison.
Perforce is not just a technically good product—it is also easy and intuitive to use. Considering the favorable licensing policy of Perforce, I recommend you download Perforce and test it for yourself.
Webinar: 8 Signs You’re Beyond Cron
11am CDT, April 29th
Join Linux Journal and Pat Cameron, Director of Automation Technology at HelpSystems, as they discuss the eight primary advantages of moving beyond cron job scheduling. In this webinar, you’ll learn about integrating cron with an enterprise scheduler.Join us!
- Not So Dynamic Updates
- New Products
- Users, Permissions and Multitenant Sites
- Security in Three Ds: Detect, Decide and Deny
- Flexible Access Control with Squid Proxy
- Tighten Up SSH
- DevOps: Everything You Need to Know
- Solving ODEs on Linux
- Non-Linux FOSS: MenuMeters
- Android Candy: Bluetooth Auto Connect