Perforce Public Depot
Perforce Utilities Project

  • Miscellany

  • About This Project

    Back to Table of Contents
    Content The Perforce Utilities Project is a collection of programs and scripts that integrate Perforce with a variety of software development tools and environments, and/or provide alternative interfaces to the Perforce SCM system.
    Curator This project is maintained by Perforce staff, with individual curators as shown below. Eventually we'll split these utilities up into separate projects, depending on their activity and growth. If you have a particular interest in any or all of this project, and would like to volunteer as a curator, please email us.

    If you would like to contribute to one of the categories that does not have a curator yet, you may request to have your submitted changes integrated into this project by emailing Perforce staff at

    Depot Browsers

    Back to Table of Contents

    perfbrowse. Shows depot hierarchies, changelists, filelogs, file contents, diffs, etc. There's a 99.1-compatible version and a 98.2-compatible version.

    P4DB. Based on perfbrowse, with added features, including labels associated with files, file content viewer with annotated deltas, HTML file viewer, and The Great Submit Race.

    Conversion Scripts

    Back to Table of Contents

    This CVS to Perforce converter extracts metadata from a CVS repository and generates a Perforce depot using Perforce client commands. The converter handles Attic/ and .cvsignore, and has flexible support for branching. Contributed by Richard Geiger, who is also its curator. (See the README file for more info.)

    Converts Visual Source Safe archives to Perforce, preserving the original times and authors. Branches are translated verbatim, individual file revisions are grouped as much as possible into Perforce's notion of atomic changes.

    Requires Perl 5, VSS 5.0 or later and Perforce 97.3 or later. Perforce makes this conversion tool available for the convenience of our customers, these scripts are not fully supported.

    Curated by Robert Cowham.

    Review Daemons

    Back to Table of Contents

    A Perforce notification review daemon written in Python, for use on Windows or Unix; can run in the background or via cron; allows users to subscribe to notifications about jobs (as well as changes); can notify admin about bad email addresses.

    A Perforce notification review daemon for Unix, written in Perl. This is the review daemon used for the Public Depot. Runs on Unix; written in perl; can run in the background or via cron; supports "cc:" in the description or client spec; can do logging; can add a hyperlinks to p4web (or some other web-based Perforce browser) to display full change information.

    A Perforce notification review daemon in Java. Contributed by David Markley.

    Pre-Submit Triggers

    Back to Table of Contents

    Perforce Release 99.1 introduced server support for pre-submit triggers. Here are some example scripts that can be used as triggers in a Perforce 99.1 (or later) server. These scripts were written and contributed by Jeff Bowles and Wes Peters.

    Script NameStatus*
    Description Example trigger to enforce a rule "submissions must be associated with a job.". Similar to above, but contributed by Wes Peters and written in Unix "shell". Takes a different approach to the problem, running "p4 fixes" to determine whether you're fixing something with this submission. A script to notice when you're creating new files (or integrating to a new branch) and the directory name you're writing the [new] file to isn't the same case as an existing directory name.

    (For example, if "//depot/x/y/z.c" exists, this won't allow you to create a file named "//depot/X/Y/one.c".) Example trigger to enforce a rule "files of suffix .x/.y need to be checked in as pairs". Example trigger to enforce a rule "submissions of .gif must binary files and .sh files should be text and...."
    simple.cmd Classroom example of writing a trigger using the Windows/NT command shell, a.k.a. "a .cmd script". (It checks that "Bug:" is included in the change description.) Doesn't do a lot, but gets the idea across.

    *How to interpret the "Status" field:

    Diffing and Merging

    Back to Table of Contents

    Some emacs lisp code to make editing merges in p4 easier.

    Defect Tracking

    Back to Table of Contents

    Compatibility Aids

    Back to Table of Contents

    c4. A CVS-like frontend to p4. This package was contributed by Neil Russell, who is also its curator. (See the README file for more info.)

    Aegis-like wrappers to p4.


    Back to Table of Contents

    p4wrapper. A set of useful commands wrapped around p4, some (but not all) with a CVS bent. Contributed and curated by Rick Richardson. (See the README file for more info.)

    Copyright ©
    1998, 1999
    Perforce Software
    You're browsing a file stored as
    $Id: //guest/perforce_software/utils/index.html#23 $
    in the Perforce Public Depot.
    Back to
    Table of