Re: [p4] [BUG] Custom tool arguments broken
P4Reg <[email protected]>
| Newsgroups | gmane.comp.version-control.perforce |
|---|---|
| Message-ID | <[email protected]> |
Posted on behalf of forum user 'P4Reg'. Hi This behaviour has been logged as known issue. As a workaround you can extract the depot path from the workspace path returned by %d or %D using the "p4 where" command (see "p4 help where") with the -F formatting option to p4 (see https://www.perforce.com/blog/130826/fun-formatting ) (no doubt there are other ways you can do it but "p4 where" is specifically designed to map between depot, client and workspaces paths). For example, for the folder path "c:\Users\Reg\Perforce\reg_reg-win8_3086\depot\cases\" p4 -ztag -F "%depotFile%" where C:\Users\Reg\Perforce\reg_reg-win8_3086\depot\cases\... ..it returns the depot path: //depot/cases/... So in a custom tool/script you can take the client path given by %d or %D and run the p4 where command on it to translate it to the depot path e.g. p4 -ztag -F "%depotFile%" where %d -- Please click here to see the post in its original format: http://forums.perforce.com/index.php?/topic/5487-bug-custom-tool-arguments-broken _______________________________________________ perforce-user mailing list - [email protected] http://maillist.perforce.com/mailman/listinfo/perforce-user