[p4] Giving each user a private sandbox
Ivey, William
william_ivey at bmc.com
Wed May 10 15:31:19 PDT 2006
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com]On Behalf Of
> Weintraub, David
> Sent: Wednesday, May 10, 2006 4:31 PM
> To: perforce-user at perforce.com
> Subject: [p4] Giving each user a private sandbox
>
>
> Is there someway to setup Perforce's protection tables to do something
> like this:
>
> write user %USER% * //depot/Private/%USER%/...
>
> So, that "bob" had permission in //depot/Private/bob/... and "tom" had
> write permission in //depot/Private/tom/..., etc.
>
> I would like to setup separate sandboxes for each user, but I really
> don't want to add 90 plus lines in my Perforce protection table to do
> this.
Could you use a submit trigger that rejected any attempt to add to
//depot/Private/X where X wasn't the submitter's ID (or, for less
control, any user's ID?) By restricting it to adds or branches,
you, as admin, could create additional directories by any name
within which they could edit existing files. Might be useful.
-Wm
More information about the perforce-user
mailing list