5 messages in com.perforce.perforce-user[p4] Alt root not getting used
FromSent OnAttachments
Chris Mitchell12 Sep 2003 11:56 
Ivey, William12 Sep 2003 12:41 
Chris Mitchell12 Sep 2003 13:22 
Ivey, William12 Sep 2003 13:44 
Leo Laksmana12 Sep 2003 13:57 
Subject:[p4] Alt root not getting used
From:Leo Laksmana (LLak@ariba.com)
Date:09/12/2003 01:57:16 PM
List:com.perforce.perforce-user

I have more luck with this scheme:

Root: /home/xxx

AltRoots: y:\home\xxx

You also want to make sure that your p4 shortcut uses y: (or the drive letter you use) to start in.

-Leo

-----Original Message----- From: Chris Mitchell [mailto:cmitchell at celitesystems.com] Sent: Friday, September 12, 2003 1:23 PM To: Ivey, William; perforce-user at perforce.com Subject: RE: [p4] Alt root not getting used

-----Original Message----- From: Ivey, William [mailto:william_ivey at bmc.com] Sent: Friday, September 12, 2003 2:42 PM To: 'perforce-user at perforce.com' Subject: RE: [p4] Alt root not getting used

At least that seems to be what I've seen when I've tried it. (I had much better success using a unix path and a network drive mapped to the same physical directory:

Root: S:\XYX

AltRoots: /opt/stuff/project/XYX

Note that it didn't work from Windows with the unix path in root since the forward slashes upset Windows. -Wm

This is exactly what we do for the same reason.

When this user does a sync it creates a dir (in unix mind you) called t:\wa\p4view and then stuffs everything in there.

So in my example, these map to the same dir:

Root:

t:\wa\p4view

AltRoots:

/home/user/wa/p4view

But after a sync the full path to the files is: /home/user/wa/p4view/t:\wa\p4view\/...

Like you, it works for me, but not for him.