The type of the depot.
Namespace: Perforce.P4Assembly: p4api.net (in p4api.net.dll) Version: 2015.1.103.4687 (2015.1.103.4687)
Syntax
| C# |
|---|
[FlagsAttribute] public enum DepotType |
| Visual Basic |
|---|
<FlagsAttribute> _ Public Enumeration DepotType |
| Visual C++ |
|---|
[FlagsAttribute] public enum class DepotType |
Members
| Member name | Value | Description | |
|---|---|---|---|
| Local | 0 | A 'local' depot (the default) is managed directly by the server and its files reside in the server's root directory. | |
| Remote | 1 | A 'remote' depot refers to files in another Perforce server. | |
| Spec | 2 | 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. | |
| Stream | 4 | A 'stream' depot is a local depot dedicated to the storage of files in a stream. | |
| Archive | 8 | An 'archive' depot defines a storage location to which obsolete revisions may be relocated. | |
| Unload | 16 | An 'unload' depot defines a storage location to which database records may be unloaded and from which they may be reloaded. |
