[p4] Using p4 protect to create a "public" user

[Oren Shemesh (oshemesh)]

I disagree - To the best of my knowledge, Perforce is perfectly fine
with having a single read-only user to be used by many people who only
need read-only access.

Regarding your original questions, I would check the latest release,
which (If I recall correctly) supports quite a few triggers related to
forms editing. You may be able to create a trigger that checks every
change to a user spec, hence prevent the public user from creating a
password, or create additional clients.

Regards, Oren. 

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of paul goffin
Sent: Thursday, October 11, 2007 8:39 AM
To: Quanah Gibson-Mount
Cc: perforce-user at perforce.com
Subject: Re: [p4] Using p4 protect to create a "public" user

You do realise what you're trying to do is directly against Perforce's
license conditions, don't you?

> I'm trying to set it up so I can have a user named "public" read just 
> one particular part of the perforce tree.  I've got this mostly 
> working, except for three issues.

(One way round this may be to use the web client as a server.  Perforce
don't seem to mind this particular way of working round their license
conditions.)

Paul.
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user