Re: [p4] How to exclude/ignore wildcard in mapping different locations in client spec
Sambwise <[email protected]>
| Newsgroups | gmane.comp.version-control.perforce |
|---|---|
| Message-ID | <[email protected]> |
Posted on behalf of forum user 'Sambwise'. Correct; the client mapping logic is deterministic, i.e. given a client view mapping any unique depot path will map to a unique workspace path and vice versa. Now, it does strike me that you could use overlay mappings here, which do permit multiple depot paths to go to one workspace path: //depot/main/C1/... //WK/... +//depot/main/C2/... //WK/... +//depot/main/C3/... //WK/... The problem with overlay mappings is that when you add a new file it defaults to the last (highest precedence) path unless you specify a different depot path; this is easy to mess up and files inevitably end up going to the wrong locations. I think explicitly specifying the mappings for each component is less of a headache. Two larger process changes I can see that would make this easier: A) Get rid of that Cn directory level. If all the components are unique across CNs, why are those even different directories? (Maybe there's a good reason that's not obvious from the example -- but if there's not, flatten that stuff out in the depot rather than trying to flatten it in the clients.) B) Use streams to manage the components so each user doesn't have to do it in their own workspace. Template clients are also an option, but streams have the advantage of updating everyone automatically whereas template-based clients will need to be manually refreshed per user. -- Please click here to see the post in its original format: http://forums.perforce.com/index.php?/topic/5458-how-to-excludeignore-wildcard-in-mapping-different-locations-in-client-spec _______________________________________________ perforce-user mailing list - [email protected] http://maillist.perforce.com/mailman/listinfo/perforce-user