      |
|
To define a client workspace:
Specify the workspace name by setting P4CLIENT; for
example, on a UNIX system:
$ export P4CLIENT=bruno_ws
Issue the p4 client command.
Stream users must pass in the S _streamname option to
the p4 client command to specify the name of
the stream to which
Helix Server
should bind the workspace.
Helix Server displays the client specification form in your text editor. (For details about Helix Server forms, see Using Helix Server forms.)
Specify (at least the minimum) settings and save the specification.
No files are synced when you create a client specification. To find out how to sync files from the depot to your workspace, see Sync files. For details about relocating files on your computer, see Change the location and/or layout of your workspace.
The minimum settings you must specify to configure a client workspace are:
Workspace name
The workspace name defaults to your computer’s hostname, but your
computer can contain multiple workspaces. To specify the effective
workspace, set P4CLIENT.
Workspace root
The client workspace root is the top directory of your client workspace, where Helix Server stores your working copies of depot files. Be sure to set the workspace root, or you might inadvertently sync files to your computer’s root directory.
For Windows users: when specifying a workspace root, you must include
the drive letter. In addition, root is null on Windows when the client
workspace is either on a disjoint drive with only c:\ as
the root and/or is spread over multiple drives.
If the workspace root directory does not exist, you must create it before the Helix Server application can make use of it.
The @, #, *, and %
characters have specific meaning to
Helix Server; if you
have file or folder names that use these characters, see
Restrictions on filenames and identifiers
for details.
By default, the entire depot is mapped to your workspace. You can define a workspace view (also referred to as a client view) to determine which files in the depot are mapped to your workspace. This enables Helix Server to construct a one-to-one mapping between individual depot and workspace files. You can map files to have different names and locations in your workspace than they have in the depot.
For users of streams,
Helix Server generates the workspace view from the contents of the stream
spec’s Paths: field. Users of classic
Helix Server
branches configure the workspace view by editing the contents of the
client spec’s View: field.
For details on configuration of workspace views, see Configure workspace views.
The client storage type cannot be changed after client workspace is created. For example, a readonly client cannot be changed into a writeable client.
| |
|