[p4] restrict user from adding files

[Gabor Maghera]

What I meant by doing it with protections is that you could list all of your
existing files and set permissions for them specifically.  It's a silly way
of doing it, I agree.

On Sun, Jul 20, 2008 at 3:23 PM, Stephen Vance <steve at vance.com> wrote:

>  You can't do it with protections. Protections don't distinguish between
> add and edit. You can only do it with a trigger.
>
> Steve
>
>
> b kumar wrote:
>
> We have some artists whom we dont want to have the ability to add new assets, which would require quite a bit of changes to be made by other teams to  but its ok for these artists to edit their files. how can i use protection table to give access to an user to edit a file (say a .jpg) but prevent that user from adding that file
>
> Thanks
> Bala
>
>
>
> Date: Sat, 19 Jul 2008 08:36:08 -0700
> From: jab at pobox.com
> To: gmaghera at gmail.com
> Subject: Re: [p4] restrict user from adding files
> CC: kba002 at hotmail.com; perforce-user at perforce.com
>
> Given that you have a history for every action, and the ability to back out work that is crummy, why bother with "edit is okay but add is not" issues?
> Except for wildly screwing up a directory tree for a short while (just long enough to delete the work and apply a salve to the participants), what is the harm that adding a file might do? (Especially since you can always replace an existing file's content with an 'edit'.)
>
> I suggest that "p4 protect" (protections) will be the way to keep people from touching things they shouldn't, and peer pressure will take care of the rest.
> Why use chloroform when a fly swatter will do?
>
>   -Jeff Bowles
> (ps. A trigger, that checks for "creating revision #1 of a file, meaning an add or branch" in the submissions, will probably deal with your "add" needs. If you still want to, that is.)
>
>
> On Fri, Jul 18, 2008 at 10:37 PM, Gabor Maghera <gmaghera at gmail.com> <gmaghera at gmail.com> wrote:
>
> You can use file names in the protection table.  Perforce's wild cards come
>
> in handy for defining patterns of files,  .../*.* would match all files with
>
> a suffix.
>
>
>
> Gabor
>
>
>
> On Fri, Jul 18, 2008 at 3:21 PM, b kumar <kba002 at hotmail.com> <kba002 at hotmail.com> wrote:
>
>
>
>
>
>    Hi
>
>
>     we would like to restrict some users in our engineering group to have just
>
>
>     edit access but shouldnt have permission to add files. I dont see any option
>
>
>     in the protections to selectively give add access to an user. I would like
>
>
>     to know if there is a simple way to do that in perforce other than having a
>
>
>     change-submit trigger.
>
>
>       Thanks
>
>
>     Bala
>
>
>         _________________________________________________________________
>
>
>     With Windows Live for mobile, your contacts travel with you.
>
>
>       http://www.windowslive.com/mobile/overview.html?ocid=TXT_TAGLM_WL_mobile_072008
>
>     _______________________________________________
>
>
>     perforce-user mailing list  -  perforce-user at perforce.com
>
>     http://maillist.perforce.com/mailman/listinfo/perforce-user
>
>    _______________________________________________
>
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
>
>
>
> --
> Stephen Vancewww.vance.com
>
>