Perforce 2006.1 Command Reference | ||
<< Previous Chapter p4 changes |
Table of Contents Index Perforce on the Web |
Next Chapter >> p4 clients |
Although there is always a one-to-one mapping between a client workspace file and a depot file, these files do not need to be stored at the same relative locations, nor must they have the same names. The client view, which is specified in the p4 client form's View: field, specifies how files in the client workspace are mapped to the depot, and vice-versa.
When called without a clientname argument, p4 client operates on the client workspace specified by the P4CLIENT environment variable or one of its equivalents. If called with a clientname argument on a locked client, the client specification is read-only.
When p4 client completes, the new or altered client workspace specification is stored within the Perforce database; the files in the client workspace are not touched. The new client view doesn't take effect until the next p4 sync.
The command p4 workspace is an alias for p4 client.
Field Name |
Type |
Description |
---|---|---|
Client: |
Read-only |
The client workspace name, as specified in the P4CLIENT environment variable or its equivalents. |
Owner: |
Writable |
The Perforce user name of the user who owns the client workspace. The default is the user who created the client workspace. |
Update: |
Read-only |
The date the client workspace specification was last modified. |
Access: |
Read-only |
The date and time that any part of the client workspace specification was last accessed by any Perforce command. |
Host: |
Writable, optional |
The name of the host machine on which this client workspace resides. If included, operations on this client workspace can be run only from this host. The hostname must be provided exactly as it appears in the output of p4 info when run from that host. This field is meant to prevent accidental misuse of client workspaces on the wrong machine. It doesn't provide security, since the actual value of the host name can be overridden with the -H flag to any p4 command, or with the P4HOST environment variable. For a similar mechanism that does provide security, use the IP address restriction feature of p4 protect. |
Description: |
Writable, optional |
A textual description of the client workspace. The default text is Created by owner. |
Root: |
Writable, mandatory |
The directory (on the local host) relative to which all the files in the View: are specified. The default is the current working directory. |
AltRoots: |
Writable, optional |
Up to two optional alternate client workspace roots. Perforce client programs use the first of the main and alternate roots to match the client program's current working directory. This enables users to use the same Perforce client specification on multiple platforms with different directory naming conventions. If you are using a Windows directory in any of your client roots, you must specify the Windows directory as your main client root and specify your other client root directories in the AltRoots: field. For example, an engineer building products on multiple platforms might specify a main client root of C:\Projects\Build for Windows builds, and an alternate root of /staff/userid/projects/build for any work on UNIX builds. |
Options: |
Writable, mandatory |
A set of seven switches that control particular client options. See the Usage Notes, below, for a listing of these options. |
LineEnd: |
Writable, mandatory |
A set of four switches that control carriage-return/linefeed (CR/LF) conversion. See the Usage Notes, below, for a listing of these options. |
View: |
Writable, multi-line |
Specifies the mappings between files in the depot and files in the client workspace. See Views for more information. |
-t clientname |
Copy client workspace clientname's view and client options into the View: and Options: field of this client workspace. (i.e, use clientname's View: as a template) |
-f |
Allows the last modification date, which is normally read-only, to be set. Can also be used by Perforce superusers to delete or modify clients that they don't own. |
-d [-f] clientname |
Delete the specified client workspace, if the client is owned by the invoking user or it is unlocked. (The -f flag allows Perforce superusers to delete locked client workspaces that they don't own.) |
-i |
Read the client description from standard input. |
-o |
Write the client specification to standard output. |
See the Global Options section. |
Option |
Choice |
Default |
---|---|---|
[no]allwrite |
If set, unopened files on the client are left writable. |
noallwrite |
[no]clobber |
If set, a p4 sync overwrites ("clobbers") writable-but-unopened files in the client that have the same name as the newly-synced files |
noclobber |
[no]compress |
If set, the data stream between the client and the server is compressed. (Both client and server must be version 99.1 or higher, or this setting is ignored.) |
nocompress |
[no]crlf |
On Windows, if crlf is set, CR/LF translation is performed automatically when copying files between the depot and the client workspace. |
crlf |
[un]locked |
Grant or deny other users permission to edit the client specification (To make a locked client specification truly effective, you should also set a the client's owner's password with p4 passwd.) If locked, only the owner is able to use, edit, or delete the client spec. Perforce administrators can override the lock by using the -f (force) flag with p4 client. |
unlocked |
[no]modtime |
For files without the +m (modtime) file type modifier:
|
nomodtime Ignored for files with the +m file type modifier. |
[no]rmdir |
If set, p4 sync deletes empty directories in a client if all files in the directory have been removed. |
normdir |
p4 client |
Edit or create the client workspace specification named by the value of P4CLIENT or its equivalents. |
p4 client -t sue joe |
Create or edit client workspace joe, opening the form with the field values and workspace options in client workspace sue as defaults. |
p4 client -d release1 |
Delete the client workspace release1. |
Perforce 2006.1 Command Reference | ||
<< Previous Chapter p4 changes |
Table of Contents Index Perforce on the Web |
Next Chapter >> p4 clients |