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'. [https://forums.perforce.com/index.php?app=forums&module=forums§ion=findpost&pid=22227] jclx, on 2017/08/17 20:34:09 UTC, said: > Assuming it isn't possible with wildcards based on the docs. > This is correct. The problem with trying to squash it down as you're describing is this. Suppose you have this mapping: //depot/main/*/Component*/... //WK/Component*/... and these depot files: //depot/main/A/ComponentA/foo //depot/main/B/ComponentA/foo //depot/main/A/ComponentB/foo Where does each one map to the workspace? (Remember that client views are one-to-one and that with the exception of overlay mappings, which are weird, they are fully deterministic without respect to the files in the depot -- you need to always be able to determine a workspace location given a depot location and vice versa, and that mapping needs to be reversible. A client view that did not have this property would scatter your files hither and yon when you did normal sync and submit operations [like overlay mappings do sometimes if you aren't careful]) -- 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