8 messages in com.perforce.revml[revml] RE: [p4] Why does p4 look at ...| From | Sent On | Attachments |
|---|---|---|
| barries | 16 May 2001 07:14 | |
| Stephen Vance | 16 May 2001 08:38 | |
| barries | 16 May 2001 08:57 | |
| Stephen Vance | 16 May 2001 09:00 | |
| Schaible, Jorg | 16 May 2001 09:03 | |
| barries | 16 May 2001 09:48 | |
| Maurice Meyer | 16 May 2001 09:49 | |
| barries | 16 May 2001 10:12 |
| Subject: | [revml] RE: [p4] Why does p4 look at PWD?![]() |
|---|---|
| From: | Maurice Meyer (MMe...@Netcentives.com) |
| Date: | 05/16/2001 09:49:48 AM |
| List: | com.perforce.revml |
I've got a call into Perforce about this since Solaris 8 cd seems to just use whatever you pass as the argument to set PWD. In the case where you CD into a soft link, you get a PWD that includes the soft link name which Perforce can't use to figure the path. If you unset PWD then p4 does the right thing and figure out the "real" working directory. I've found it necessary to have a wrapper that unsets PWD before running p4. On solaris 8, I'd consider this a mis-feature but only since it trusts something it should be able to which I consider broken.
Maurice
-----Original Message----- From: barries [mailto:barr...@slaysys.com] Sent: Wednesday, May 16, 2001 7:15 AM To: perf...@perforce.com; rev...@perforce.com Subject: [p4] Why does p4 look at PWD?
In writing the vcp wrapper for p4, I overlooked the fact that the p4 client prefers to take it's notion of current working directory from the PWD environment variable instead of the actual working directory. (Kudos to Matthew Attaway for much help debug this).
My question is: is this a feature or possibly a misfeature?
- Barrie
_______________________________________________ perforce-user mailing list - perf...@perforce.com http://maillist.perforce.com/mailman/listinfo/perforce-user




