[p4] Giving each user a private sandbox

[Shawn Hladky]

Do you really need that level of control?  We have user depot setup with
folders for each user.  Everyone has full read/write on the entire user
depot, and in over 2 years we've had no incidence of abuse.



The way I see it, if Tom messes with Bob's stuff, why not let Tom and Bob
hash it out mano a mano.  There's no way Tom can do it w/o full history, and
it's easy for Bob un-do anything Tom does.  And it's quite likely that they
want to share the directory intentionally.



At least that's the way it works here... a company w/ 100 users in a
couple geographic locations.  With thousands of users and dozens of offices,
it may get more complicated.



On 5/10/06, Weintraub, David <david.weintraub at bofasecurities.com> wrote:
>
> 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.
>
> My biggest fear isn't Bob messing around with Tom's private directory,
> it's Bob, Tom, and everyone else deciding they could use more than one
> private directory, so I end up with thousands of directories under
> //depot/Private instead of one for each user. I'd be satisfied with
> users being able to write to //depot/Private/*/..., but not be able to
> create another directory under //depot/Private if it previously didn't
> exist.
>
> Has anyone done anything like this?
>
> --
> David Weintraub
> david.weintraub at bankofamerica.com
> david.weintraub at bofasecurities.com
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>