Perforce 2002.2 Command Reference | ||
<< Previous Chapter p4 delete |
Table of Contents Index Perforce on the Web |
Next Chapter >> p4 depots |
In the latter case, referred to as the use of remote depots, the Perforce client's default Perforce server (i.e. the machine specified in P4PORT) allows the Perforce client to access a remote Perforce server, so the client doesn't need to know where the files are actually stored. Remote depots are restricted to read-only access. Thus, a Perforce client program can't add, edit, delete, or integrate files that reside in the depots on the other servers. For more information about remote depots, see the Perforce User's Guide and the Perforce System Administrator's Guide.
To create or edit a depot, use p4 depot depotname and edit the fields in the form.
Field Name |
Type |
Description |
---|---|---|
Depot: |
Read-Only |
The depot name as provided in p4 depot depotname. |
Owner: |
Writable |
The user who owns the depot. By default, this is the user who created the depot. |
Description: |
Writable |
A short description of the depot's purpose. Optional. |
Type: |
Writable |
local or remote. Local depots are writable; remote depots are proxies for depots residing on other servers, and cannot be written to. |
Address: |
Writable |
If the Type: is local, the address should be the word subdir. If the Type: is remote, the address should be the P4PORT address of the remote server. |
Map: |
Writable |
If the Type: is local, the map should be the relative location of the depot subdirectory relative to the Perforce server's P4ROOT. It must contain the ... wildcard; for example, a local depot foo might have a Map: of foo/... . If the Type: is remote, the map should be a location in the remote depot's physical namespace, for example, //depot/foo/bar/... . This directory will be the root of the local representation of the remote depot. |
-d depotname |
Delete the depot depotname. The depot must not contain any files; the Perforce superuser can remove files with p4 obliterate. If the depot is remote, p4 obliterate must still be run: no files are deleted, but any outstanding client or label records referring to that depot are eliminated. |
-i |
Read a depot specification from standard input. |
-o |
Write a depot specification to standard output. |
See the Global Options section. |
Perforce 2002.2 Command Reference | ||
<< Previous Chapter p4 delete |
Table of Contents Index Perforce on the Web |
Next Chapter >> p4 depots |