[p4] Mapping of development setup files

[Ivey, William]

If you create the client with a null root (literally
the word "null") then each view mapping line can refer
to whatever location it wants, including spanning drives
on Windows:

//depot/somedir/...  //myclient/G:/mywork/somedir/...
//depot/otherdir/...  //myclient/C:/stuff/otherdir/...

But if you don't like the idea of making C:\ your root,
you will probably like this even less.

A second workspace makes more sense to me. These changes
are not part of your active source, but are supporting 
changes, so they logically deserve a workspace of their
own.

-Wm

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of
todd.benham at kodak.com

We have several cases where files need to be modified and tracking in
version control and then mapped outside the typical workspaces.
 
Say a typical workspace root is 
 
c:\ws_todd\
 
Not we have certain compilers and other OS files that are modified from
the original install. We only track the one that changed from the
original. In VSS, we simply mapped these (by overriding the default
location) to the right locations and developer would sync those on a
daily
basis (even though they rarely changed). 
 
These kind of files might be in a directories such as 
 
c:\compiler\inc
c:\rtos\inc
 
As best I can tell, this is impossible to map in one perforce workspace
(unless root is c:\ which is highly discouraged).
 
My current solution would be to
 
1) Create a script that uses filespecs and p4 sync to map the
appropriate
files from a somewhat arbitrary location in the depot.
 
2) Another thought is to have a second workspace that could be sync'd
when
the development environment is set up or something changes.
 
In each case, it becomes a multi-step process and potentially error
prone
if forgot. This is not too bad since we have automated builds so a least
the that can enforce the 2 steps.
 
Does anyone have other suggestions?
 
Todd 
 
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user