4 messages in com.perforce.perforce-userclient view mapping question| From | Sent On | Attachments |
|---|---|---|
| Bruc...@sattel.com | 01 Feb 1999 11:49 | |
| Long...@mindq.com | 01 Feb 1999 11:59 | |
| Bruc...@sattel.com | 02 Feb 1999 10:10 | |
| Step...@vance.com | 02 Feb 1999 20:53 |
| Subject: | client view mapping question |
|---|---|
| From: | Bruc...@sattel.com (Bruc...@sattel.com) |
| Date: | 02/02/1999 10:10:59 AM |
| List: | com.perforce.perforce-user |
Try... //depot/rel/... /work/proj/... -//depot/rel/e/... /work/proj/e/... //depot/dev/e/... /work/proj/e/...
Notice the dash (-)
That's fine for this simple example, but I have many such directories so it'd end up looking like:
//depot/rel/... /work/proj/... -//depot/rel/e/... /work/proj/e/... //depot/dev/e/... /work/proj/e/... -//depot/rel/f/... /work/proj/f/... //depot/dev/f/... /work/proj/f/... -//depot/rel/g/... /work/proj/g/... //depot/dev/g/... /work/proj/g/... -//depot/rel/h/... /work/proj/h/... //depot/dev/h/... /work/proj/h/...
which is what I'm trying to avoid.
What I need to a simple syntax to get everything in a depot branch to override anything that's already mapped and comflicts.
- -Bruce.
Long.
-----Original Message----- From: Bruce Edge <bedge at sattel.com> To: Perforce Users <perforce-user at perforce.com> Date: Monday, February 01, 1999 2:47 PM Subject: client view mapping question
I'd like to use the concept of a development client and a release client. The dev and rel clients would have separate trees in the depot for binaries.
I'd like the dev client to be a subset of the rel client. ie: the rel client would contain all files needed for a runtime system, while the dev client would contain all the same files as the dev client, but override a few files/directories with development versions. So, all files not explicitly specified to come from the dev client would come from the rel area.
The depot contains:
//depot/rel/a //depot/rel/b //depot/rel/c //depot/rel/d //depot/rel/e ..and.. //depot/dev/e
I'd like to pick up everything from //depot/rel, except dev/e which would come from the //depot/dev by specifying a mapping like:
//depot/rel/... /work/proj //depot/dev/... /work/proj (dirs present in //depot/dev override those in //depot/rel)
not:
//depot/rel/a... /work/proj/a //depot/rel/b... /work/proj/b //depot/rel/c... /work/proj/c //depot/rel/d... /work/proj/d //depot/dev/e... /work/proj/e
in my client.
Not a big issue in this contrived example, but a very big deal in a project with a complex tree structure.
Can this be done?
TIA, Bruce.