A closer look at a remote spec
The following is a sample remote spec, describing a remote named
server-main-darwin
:
# A Helix Remote Specification. RemoteID: server-main-darwin Owner: bruno Options: unlocked compress Update: 2014/11/21 08:21:32 Description: A fairly complete set of the mainline code for the widget, with the test harness limited to the darwin platform. Fetch or clone from this remote spec if you want to build and work with the mainline widget code on a darwin machine. LastFetch: default LastPush: default DepotMap: //stream/main/widget/... //depot/main/widget/... //stream/main/widget-test/server/... //depot/main/widget-test/server/... //stream/main/widget-test/bin/... //depot/main/widget-test/bin/... -//stream/main/widget-test/bin/arch/... //depot/main/widget-test/bin/arch/... //stream/main/widget-test/bin/arch/darwin90x86_64/... //depot/main/widget-test/bin/arch/darwin90x86_64/... //stream/main/widget-doc/code/... //depot/main/widget-doc/code/...
The following table describes the remote spec in more detail:
Entry | Meaning |
---|---|
|
The remote identifier. |
|
The |
|
The user who created this remote. |
|
The |
|
The date this specification was last modified. |
|
The date of the last push or fetch on this remote. |
|
A short description of the shared server (optional). |
|
The last changelist that was fetched. If set to default, means no fetches have yet occurred. |
|
The last changelist that was pushed. If set to default, means no pushes have yet occurred. |
|
The lines to map local files to remote files. The file paths on the left-hand side are on the personal server. The file paths on the right-hand side are on the shared server. |
Remote specs give you the full power of Helix Server client view syntax. For details, see the section "Define a client workspace" in the chapter Configure clients in the Helix Core Command-Line (P4) Guide.