[p4] protect and where

Stephen Vance steve at vance.com
Tue Oct 30 16:00:57 PST 2001

Since your client spec is so simple, it appears that multiple protection 
lines can cause the same effect Chuck mentions.  Have you talked to Support 

At 07:21 AM 10/30/2001 -0800, Chuck Karish wrote:
>At 09:37 AM 10/29/2001 -0800, Mike Castle wrote:
> >On Sat, Oct 27, 2001 at 09:46:34AM -0700, Chuck Karish wrote:
> >> This isn't documented in either doc set (p4 help, Command Reference).
> >> File a bug against the docs and fix your scripts; a user could break them
> >> by changing a client spec.
> >
> >How could changing a client spec affect this?
>If multiple lines in the client spec refer to the file, then there will be 
>lines in the 'p4 where' output.   For example, a file might be referenced by
>its parent directory, then by a line that excludes it from the spec, then by a
>line that maps it to a different place.  Two lines will come up when you do
>'p4 where'.
> >The whole purpose of running the p4 where in the build script is to find
> >out where something is mapped into the file system.
>Then your script must become a bit smarter.
>Chuck Karish            karish at well.com           (415) 317-0182
>perforce-user mailing list  -  perforce-user at perforce.com

Stephen Vance
mailto:steve at vance.com

More information about the perforce-user mailing list