[p4] P4V and check out of a binary file not at latest revision

Jeff Grills jgrills at junctionpoint.com
Fri Apr 13 09:52:53 PDT 2007


I worked on a project in the past where it was necessary for multiple users
to be able to work on a binary file at the same time, but the format was
such that it was relatively easy for us to write a custom diff/merge
application for that file type.  We did, and it worked out quite well.
Unfortunately usability was an issue because at the time perforce couldn't
be configured to launch a specific merge program based on the file extension
as it could for diff.  Since then, though, perforce has added that
functionality to its graphical clients.  They require relatively new
versions of perforce, though.  Culled from the release notes:

Minor new functionality in 2007.1

    #108261 *
        P4V now has the ability to configure 3rd party merge tools by 
        extension type. Additionally, P4V now supports the ability to 
        configure arguments for 3rd party diff tools. These properties
        are now saved in an XML settings file.
        (Sir #13932)

Other New Functionality in 2006.2

     #102044
         P4Win now has the ability to specify which merge program to use for
a 
         given file type.  The Settings > Options > Merge pane has a list of

         extensions and associated merge programs. (Job #14422 - SIR)
         
Since these are GUI client options, I would suspect that users could upgrade
their client software and obtain this functionality without needing to
upgrade the server.  (In fact, that's what the '*' means for the p4v release
notes, but the p4win release notes don't specifically indicate that, but it
certainly makes sense).

j

> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Stephen Vance
> Sent: Thursday, April 12, 2007 11:07 PM
> To: Francis Paulin
> Cc: Nancy Nadeau; perforce-user at perforce.com
> Subject: Re: [p4] P4V and check out of a binary file not at 
> latest revision
> 
> Another option is to use P4V or P4Win to define an external 
> diff application. A small script that invokes the standard 
> diff or an image-specific diff tool based on extension would 
> be an appropriate way for you to have the best of both 
> worlds. You would have to configure the UIs to allow merge of 
> binaries.
> 
> Steve


More information about the perforce-user mailing list