[p4] Locking Directory

steve at vance.com steve at vance.com
Wed Aug 8 20:43:03 PDT 2007


The exclusions need to go beneath the higher level directory rules.
Algorithmically, scan from the bottom up to figure out which rule applies
when there are exclusionary maps. That's why the last rule should be your
'super' rule.

Steve

Original Message:
-----------------
From: Cameron, Ron ron.cameron at pearson.com
Date: 	Wed, 8 Aug 2007 11:27:14 -0500
To: steve at vance.com, perforce-user at perforce.com
Subject: RE: [p4] Locking Directory


Morning Steve,

Thank you fro the response.  I am still having problems.  I am sending
along a sample of what I need.  The directory will not be used by anyone
any more, they just want it there for reference. This is what I did so
far: 

There original entry: 

	write group portal_pm.g * //pem_rd/portal/...
	write group portal_iter1.g * //pem_rd/portal/...
	read group portal_read.g * //pem_rd/portal/...

The new entry: 

	write group portal_pm.g *
-//pem_rd/portal/development/code/bea-8.1/...
	write group portal_iter1.g *
-//pem_rd/portal/development/code/bea-8.1/...
	write group portal_pm.g * //pem_rd/portal/...
	write group portal_iter1.g * //pem_rd/portal/...
	read group portal_read.g * //pem_rd/portal/... 

What do I need to do? Thanks

Thanks, 
Ron Cameron 
Software Tools Administrator 
Teamtrack, Changeman, Perforce, Rally, Chalkboard, and XPlanner 
Pearson 
2510 North Dodge Street 
Iowa City, Iowa 52245-9945 
Work Phone: 319-358-4481 
Work Email: ron.cameron at pearson.com 
Work Mail Drop: 125 
Work Cubical Number: J212 


-----Original Message-----
From: steve at vance.com [mailto:steve at vance.com] 
Sent: Tuesday, August 07, 2007 5:55 PM
To: Cameron, Ron; perforce-user at perforce.com
Subject: RE: [p4] Locking Directory

Hi, Ron --

There only one good way to do it that I can think of off hand.

The first is with the protections table. The model is that you take away
everything with a '-' mapping then give back what you want to grant
('read'
or 'open' in this case, depending on whether you want to allow checkouts
for experimentation) when the directory is a sub-directory of something
with broader permissions. The following abbreviated example should
communicate the point:

read group everyone //depot/...
write group everyone -//depot/readonly/...
read group everyone //depot/readonly/...

There really isn't a trigger type for checkouts, although you could use
one of the change triggers if you don't mind people having it open for
edit.

You could use 'p4 lock' to prevent submission, but that would only cover
things that already exist. You could modify the typemap to add +l to the
file type for things in that tree, but then you'd have to check them out
to prevent others from checking them in, and it wouldn't prevent the
addition of new files, potentially with user-overridden file types.

Steve

Original Message:
-----------------
From: Cameron, Ron ron.cameron at pearson.com
Date: 	Tue, 7 Aug 2007 15:42:53 -0500
To: perforce-user at perforce.com
Subject: [p4] Locking Directory


Hi,
 
I am having a problem and after doing some research, I have not found
the solution. I understand about locking files or placing the attribute
-l on the files themselves.  I want to make a directory only readable. I
know I can place a "-" in front of the group in the protect table, but I
don't want to effect other access for a particular group.  I want to
make the directory non-writable for everyone, but accessible for read
only.  Is there a way to do this?
 
Ron 

************************************************************************
****

This email may contain material confidential to Pearson.  If you were
not an intended recipient, please notify the sender and delete all
copies. 
We may monitor email to and from our network. 
************************************************************************
****
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user


--------------------------------------------------------------------
mail2web.com - Enhanced email for the mobile individual based on
Microsoft(r)
Exchange - http://link.mail2web.com/Personal/EnhancedEmail


****************************************************************************

This email may contain material confidential to
Pearson.  If you were not an intended recipient, 
please notify the sender and delete all copies. 
We may monitor email to and from our network. 
****************************************************************************


--------------------------------------------------------------------
mail2web LIVE – Free email based on Microsoft® Exchange technology -
http://link.mail2web.com/LIVE





More information about the perforce-user mailing list