View Single Post
  #1  
Old 04-28-2005, 06:27 PM
epu epu is online now
Registered User
 
Join Date: 10-29-2003
Location: San Francisco, CA
Posts: 29
perforce action global options tab uses PWD for Root: even when it's not exported?

Hey,

I am using a perforce action that runs p4 client with Global options tab > Working folder: set to a value.

I also have PWD set as a project macro, and it isn't exported (the output of '%DOSCMD% set' doesn't show PWD is set).

However, the Root: of my p4 client is always being set to PWD, even though it's not exported.

I think perforce actions shouldn't use perforce-related macro values of PWD unless it is exported for external programs, or that explicitly setting a value in the perforce action should override the macro setting. Currently, at least for PWD, having it set in macros overrides the entry in the action.

I am working around this by setting a temp PWD macro before I use the perforce action, but this shouldn't be necessary.

Thanks again for a good product.

Best,
-e

oh yeah, I am using v5.7

Last edited by epu; 04-28-2005 at 06:29 PM.
Reply With Quote