[p4] Sharing client spec between users
PGeorgiades at lucasarts.com
Tue Dec 4 10:11:47 PST 2001
We do have such a setup in our team, but we use it for users who need
"Read-Only" access to the database. [The host machine is attached to
expensive game development hardware that we can't afford to have deployed
one per client. Thus, our users make it part of their routine to sync at
this client after submitting from their own machines and verify that
everything works on the target hardware.]
LucasArts Entertainment Company
From: steve at vance.com [mailto:steve at vance.com]
Sent: Tuesday, December 04, 2001 12:41 AM
To: johan.nilsson at esrange.ssc.se; perforce-user at perforce.com
Subject: Re: [p4] Sharing client spec between users
The first question has to be "Why?" If there isn't a
compelling reason or sufficient constraints to address the
negatives, don't do it.
That said, it can be done. You will have the issues of
both users editing the same file. You will also have the
interesting effect that the two users will have different
default changelists, even in the same workspace.
If part of the motivation is to avoid a single user having
to switch identities or clients, you can use the P4CONFIG
mechanism to simplify the process.
Your later mention about using +l won't do anything for
you. It only affects locking at the depot level, not at
the host OS level. I won't prevent mutual editing of the
Basically, if the usage is read-only or if the two users'
usage is exclusive either by time (using changelist
creation/submission as the transaction boundaries) or by
source (i.e. they use entirely different directories) and
you're not concerned about cross-contamination due to
syncs, you can do it safely.
If you want a safer approach to the source exclusive
scenario, put two clients, each for a subset of the source,
under a directory tree that reflects the whole space. A
safer approach to time exclusivity is just to create
different workspaces. If it's about disk space, just use
> supposing two different users are working on the same
machine, can they
> share a common client specification? If possible, are
there any problems to
> be aware of?
> // Johan
> perforce-user mailing list - perforce-user at perforce.com
This message was sent using WebMail by CyberGate.
perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user