[p4] Finding the workspace name: is p4config mandatory?

Ivey, William william_ivey at bmc.com
Fri Feb 22 08:55:57 PST 2008

Anything that runs from the command line is going to need information
about P4 either from the environment, it's own command line or the
registry on Windows.

I use P4CONFIG on all my build machines - I don't see what's hard
about putting one file per workspace down. Once that's done, the
script can find the client name by parsing the output from p4 info
or p4 client -o, etc.


-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Steve M.


A recent thread on this list concerns adding a changelist number to
C++ code, to which Robert Cowham responded with a suggestion to run a
couple of p4 commands in the root of the workspace [1].  This is easy
to script, but it assumes that the workspace name is available to the

As a build manager, I would prefer to write one script to be used by
all developers.  Each developer has their own workspace, so the
workspace name cannot be embedded in the script.  Therefore it seems
that the script has to obtain it from the environment.  So either you
have to have it set in the environment (but then who uses just one
client?) or you have to have a p4config file properly set up.

Is that the case -- or is there another possibility that I'm
overlooking?  Is p4config therefore mandatory even for a shop that
otherwise uses p4v exclusively?

Now, if p4config is mandatory, is there a way to generate them
automatically?  I have been crafting each of mine by hand, which is
a real nuisance.  It strikes me that the first "p4 sync" could write 
the config file for me.



More information about the perforce-user mailing list