3 messages in com.perforce.perforce-user[p4] Viewing multiple depots via P4Win
FromSent OnAttachments
Paul O'Connor22 Jul 2002 10:29 
Jim Hanrahan22 Jul 2002 11:37 
Jeffrey Jensen22 Jul 2002 13:14 
Subject:[p4] Viewing multiple depots via P4Win
From:Jeffrey Jensen (JJEN@agribank.com)
Date:07/22/2002 01:14:43 PM
List:com.perforce.perforce-user

I received a semi-clear explanation when trying to solve a different problem that helps explain why "p4 depot depot" fixes something.

We do not have a depot named "depot", but it looks like we do - a depot named "depot" still shows up now and then. It does not show up in the list of depots, but it does show up in the default list of views/maps (e.g. new clientspecs, labels, branchspecs)! So we have to delete it each time (talk about confusion for the newbies!).

I worked through not having depot "depot" showing with a Perforce support engineer. He created a bug report as there was no workaround ("p4 depot -d depot" has no effect").

Here is the enlightening part: He said that dept "depot" always exists and deleting it was not possible as Perforce uses depot "depot" for some type of internal things.

In my words, the depot "depot" mostly exists "out of the box", and executing "p4 depot depot" firmly creates it.

"Jim Hanrahan" <j.hanrahan at advantest-ard.com> 07/22/02 01:37PM >>>

I just had this problem. I talked to Perforce tech support and they are aware of this problem AND have an easy workaround:

p4 depot depot

This was run as administrator but I wasn't sure if that was required.

Somehow when you add a new depot it loses information regarding the default depot. By running this you regain that information and all depots become visible.

Don't ask me how, it just worked!

Thanks! Jim

-----Original Message----- From: perf@perforce.com [mailto:perforce-user-admin at perforce.com]On Behalf Of Paul O'Connor Sent: Monday, July 22, 2002 10:30 AM To: perforce-user at perforce.com Subject: [p4] Viewing multiple depots via P4Win

All,

I'm having trouble viewing multiple depots through P4Win. I started with a single mapping to the only depot on the server which has worked up to now. I added a new depot to the server and added a new mapping into the client view. Only the second depot is now shown. Here's the client view:

Root: e:\ Options: noallwrite noclobber nocompress crlf unlocked nomodtime normdir View: //depot/xxx/rrr/... //host/xxx/rrr/... //another/aaa/bbb/... //host/aaa/bbb/...

The client I'm running is on Windows 2000 service pack 2, the server on Solaris 2.8. A command line p4 sync sync's both depots correctly so the client spec is correct. P4Win however only shows me the latest depot I created. I upgraded to version 2002.1 34617 Jun 28 2002 but this doesn't correct the problem. The server version I'm connecting to is 2000.2 21084 (2001/03/08).

Even if I remove the second mapping for the second depot from my client view leaving what I had originally, I still get the second depot shown even after a P4Win restart.

I've looked at the docs, release notes and archives but didn't spot this issue mentioned. I don't see anything in the registry that I could change either. Any ideas?