[This is preliminary documentation and is subject to change.]
Create a new depot in the repository.
Namespace: Perforce.P4Assembly: p4api.net (in p4api.net.dll) Version: 2012.2.63.1250 (2012.2.63.1250)
Syntax
C# |
---|
public Depot CreateDepot( Depot depot, Options options ) |
Visual Basic |
---|
Public Function CreateDepot ( _ depot As Depot, _ options As Options _ ) As Depot |
Visual C++ |
---|
public: Depot^ CreateDepot( Depot^ depot, Options^ options ) |
Parameters
- depot
- Type: Perforce.P4..::..Depot
Depot specification for the new depot
- options
- Type: Perforce.P4..::..Options
The '-i' flag is required when creating a new depot
Return Value
The Depot object if new depot was created, null if creation failed
Remarks
The '-i' flag is added if not specified by the caller
p4 help depot
depot -- Create or edit a depot specification
p4 depot name
p4 depot -d name
p4 depot -o name
p4 depot -i
Create a new depot specification or edit an existing depot
specification. The specification form is put into a temporary file
and the editor (configured by the environment variable $P4EDITOR)
is invoked.
The depot specification contains the following fields:
Depot: The name of the depot. This name cannot be the same as
any branch, client, or label name.
Owner: The user who created this depot.
Date: The date that this specification was last modified.
Description: A short description of the depot (optional).
Type: 'local', 'stream', 'remote', 'spec', or 'archive'.
A 'local' depot (the default) is managed directly by
the server and its files reside in the server's root
directory.
A 'stream' depot is a local depot dedicated to the
storage of files in a stream.
A 'remote' depot refers to files in another Perforce
server.
A 'spec' depot automatically archives all edited forms
(branch, change, client, depot, group, job, jobspec,
protect, triggers, typemap, and user) in special,
read-only files. The files are named:
//depotname/formtype/name[suffix]. Updates to jobs made
by the 'p4 change', 'p4 fix', and 'p4 submit' commands
are also saved, but other automatic updates such as
as access times or opened files (for changes) are not.
A server can contain only one 'spec' depot.
A 'archive' depot defines a storage location to which
obsolete revisions may be relocated.
Address: For remote depots, the $P4PORT (connection address)
of the remote server.
Suffix: For spec depots, the optional suffix to be used
for generated paths. The default is '.p4s'.
Map: Path translation information, in the form of a file
pattern with a single ... in it. For local depots,
this path is relative to the server's root directory
(Example: depot/...). For remote depots, this path
refers to the remote server's namespace
(Example: //depot/...).
The -d flag deletes the specified depot. If any files reside in the
depot, they must be removed with 'p4 obliterate' before deleting the
depot.
The -o flag writes the depot specification to standard output. The
user's editor is not invoked.
The -i flag reads a depot specification from standard input. The
user's editor is not invoked.
p4 help depot
depot -- Create or edit a depot specification
p4 depot name
p4 depot -d name
p4 depot -o name
p4 depot -i
Create a new depot specification or edit an existing depot
specification. The specification form is put into a temporary file
and the editor (configured by the environment variable $P4EDITOR)
is invoked.
The depot specification contains the following fields:
Depot: The name of the depot. This name cannot be the same as
any branch, client, or label name.
Owner: The user who created this depot.
Date: The date that this specification was last modified.
Description: A short description of the depot (optional).
Type: 'local', 'stream', 'remote', 'spec', or 'archive'.
A 'local' depot (the default) is managed directly by
the server and its files reside in the server's root
directory.
A 'stream' depot is a local depot dedicated to the
storage of files in a stream.
A 'remote' depot refers to files in another Perforce
server.
A 'spec' depot automatically archives all edited forms
(branch, change, client, depot, group, job, jobspec,
protect, triggers, typemap, and user) in special,
read-only files. The files are named:
//depotname/formtype/name[suffix]. Updates to jobs made
by the 'p4 change', 'p4 fix', and 'p4 submit' commands
are also saved, but other automatic updates such as
as access times or opened files (for changes) are not.
A server can contain only one 'spec' depot.
A 'archive' depot defines a storage location to which
obsolete revisions may be relocated.
Address: For remote depots, the $P4PORT (connection address)
of the remote server.
Suffix: For spec depots, the optional suffix to be used
for generated paths. The default is '.p4s'.
Map: Path translation information, in the form of a file
pattern with a single ... in it. For local depots,
this path is relative to the server's root directory
(Example: depot/...). For remote depots, this path
refers to the remote server's namespace
(Example: //depot/...).
The -d flag deletes the specified depot. If any files reside in the
depot, they must be removed with 'p4 obliterate' before deleting the
depot.
The -o flag writes the depot specification to standard output. The
user's editor is not invoked.
The -i flag reads a depot specification from standard input. The
user's editor is not invoked.