[This is preliminary documentation and is subject to change.]

The type of the depot.

Namespace: Perforce.P4
Assembly: p4api.net (in p4api.net.dll) Version: 2012.2.63.1250 (2012.2.63.1250)

Syntax

C#
[FlagsAttribute]
public enum DepotType
Visual Basic
<FlagsAttribute> _
Public Enumeration DepotType
Visual C++
[FlagsAttribute]
public enum class DepotType

Members

Member nameValueDescription
Local0 A 'local' depot (the default) is managed directly by the server and its files reside in the server's root directory.
Remote1 A 'remote' depot refers to files in another Perforce server.
Spec2 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.
Stream4 A 'stream' depot is a local depot dedicated to the storage of files in a stream.
Archive8 An 'archive' depot defines a storage location to which obsolete revisions may be relocated.

See Also