[p4] Client confusion
Russell C. Jackson
rusty at rcjacksonconsulting.com
Wed Oct 5 12:10:32 PDT 2005
If you are running 2004.2 or later, you can enable a spec depot on your
server. The spec depot automatically versions all Perforce specs. You could
then put a review on the client directory, or just a particular file in that
directory to monitor changes to the client(s).
To create the spec depot, run:
p4 depot <name_you_want_for_your_new_depot>
Then in the form that comes up, change the type to spec and save it. I call
my depot spec_archives, but it doesn't matter what you call it, as long as
you make it type spec.
There is more info. on spec depot in the 2005.1 system administrator's
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Jonathan Arnold
Sent: Wednesday, October 05, 2005 10:39 AM
To: 'perforce-user at perforce.com'
Subject: [p4] Client confusion
Because there doesn't seem to be an easy way to share clients between users,
we keep running into various client-specific problems. One of the most
annoying is when a user adds a new line to their View and not telling anyone
else. When the other developers try to use their clients for the same
projects, the project doesn't compile any more. Or, even worse, it still
compiles, but now they are working off different code bases.
I'm sure this has come up before, but it would be nice if there was some way
to have system wide clients, where everyone shares the same view, only it is
relative to themselves. Or maybe some way to have a templated client, that
automagically picks up changes from everyone else.
But in the meantime, is there any easy way to track client changes?
I'd even be satisfied if there were some kind of trigger or something that
would email me whenever someone changes their client.
Jonathan Arnold (mailto:jdarnold at buddydog.org)
Jiggle The Handle, a personal blog http://jiggle.anaze.us
Procrastination is the art of keeping up with yesterday.
- Don Marquis
perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user