{"id":4588,"date":"2018-01-09T07:19:00","date_gmt":"2018-01-09T07:19:00","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/?p=4588"},"modified":"2018-09-28T12:00:48","modified_gmt":"2018-09-28T12:00:48","slug":"how-to-setup-p4-in-linux-unix","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/how-to-setup-p4-in-linux-unix\/","title":{"rendered":"How to Setup p4 in Linux \/ Unix"},"content":{"rendered":"

How to Setup p4 in Linux \/ Unix<\/strong>
\nWell many people have these questions to me that they are facing issues setting up p4 client in Linux or Unix. The Solution is pretty much straight forwards but sometimes we miss some of things which delay the setup process.
\nHere I have tried to points out these already available on Perforce Knowledge base site.
\nDownload and Installations:<\/strong><\/p>\n\n\n\n
1.<\/td>\n<\/a>Download the\u00a0p4 executable file from the Perforce web site:<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

<\/a>http:\/\/www.perforce.com\/perforce\/downloads\/index.html\u00a0<\/a>
\n<\/a>The Perforce client programs are typically downloaded to\u00a0\/usr\/local\/bin.<\/p>\n\n\n\n
2.<\/td>\n<\/a>Make the\u00a0p4 file executable (chmod +x p4)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Perforce Configuration and Workspace Setting<\/strong>
\nMethod 1<\/strong>
\nUsing Config Files:<\/strong>
\n<\/a>Config files\u00a0are text files containing Perforce settings that are in effect for files in and below the directory where the config file resides. Config files are useful if you have multiple client workspaces on the same machine. By specifying the settings in config files, you avoid the inconvenience of changing system settings every time you want to work with a different work-space.
\n<\/a>To use config files, you define the\u00a0P4CONFIG environment variable, specifying a file name (for example, .p4config). When you issue a command, Perforce searches the current working directory and its parent directories for the specified file and uses the settings it contains (unless the settings are overridden by command-line flags).
\nP4CONFIG = .p4config
\n<\/a>Each setting in the file must be specified on its own line, using the following format:
\n<\/a>setting=value<\/p>\n

<\/a>The following settings can be specified in a config file.<\/p>\n\n\n\n\n\n\n\n\n\n
<\/a>Setting<\/td>\n<\/a>Description<\/td>\n<\/tr>\n
<\/a>P4CLIENT<\/td>\n<\/a>Name of the current client workspace.<\/td>\n<\/tr>\n
<\/a>P4EDITOR<\/td>\n<\/a>The editor invoked by those Perforce commands that use\u00a0forms.<\/td>\n<\/tr>\n
<\/a>P4HOST<\/td>\n<\/a>Hostname of the client workstation. Only useful if the\u00a0Host: field of the current client workspace has been set in the p4 client form.<\/td>\n<\/tr>\n
<\/a>P4PASSWD<\/td>\n<\/a>Supplies the current Perforce user’s password for any Perforce\u00a0client command.<\/td>\n<\/tr>\n
<\/a>P4PORT<\/td>\n<\/a>The host and port number of the Perforce server or proxy with\u00a0which to communicate.<\/td>\n<\/tr>\n
<\/a>P4USER<\/td>\n<\/a>Current Perforce user name.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

For details about these settings, refer to the Perforce Command Reference.<\/p>\n

Example:<\/strong>\u00a0<\/a>Using config files to handle switching between two workspaces
\n<\/a>Ona switches between two workspaces on the same machine. The first workspace is\u00a0ona-ash. It has a client root of \/tmp\/user\/ona and connects to the Perforce server at ida:1818. The second workspace is called ona-agave. Its client root is \/home\/ona\/p4-ona, and it uses the Perforce server at warhol:1666.<\/p>\n

Rama sets the P4CONFIG environment variable to .p4config. She creates a file called .p4config in \/tmp\/user\/rama containing the following text:
\n<\/a>P4PORT=ida:1818
\nP4CLIENT=ona-ash<\/p>\n

She creates a second .p4config file in\/home\/rama\/p4-ona. It contains the following text:
\n<\/a>P4PORT=warhol:1666
\nP4CLIENT=ona-agave<\/p>\n

Any work she does on files under \/tmp\/user\/rama is managed by the Perforce server at ida:1818 and work she does on files under \/home\/rama\/p4-ona is managed by the Perforce server at warhol:1666.<\/p>\n

Method 2: Environment Variable Setting<\/strong><\/p>\n

<\/a>To configure server connection settings using environment variables, set\u00a0P4PORT to host:port, as in the following examples.<\/p>\n\n\n\n\n\n
<\/a>If the server is running on<\/td>\n<\/a>and is listening to port<\/td>\n<\/a>set P4PORT to<\/td>\n<\/tr>\n
<\/a>your computer<\/td>\n<\/a>1666<\/td>\n<\/a>localhost:1666<\/td>\n<\/tr>\n
<\/a>perforce<\/td>\n<\/a>1666<\/td>\n<\/a>1666<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Example:<\/strong>
\nexport P4PORT=X.X.X.X\\:1667
\nexport P4PASSWD=pass
\nexport P4USER=user
\nexport P4CLIENT=Sonar
\nexport PATH<\/p>\n

<\/a>Defining client workspaces<\/strong>\u00a0<\/strong>
\n<\/a>To define a client workspace:<\/p>\n\n\n\n
1.<\/td>\n<\/a>Specify the workspace name by setting\u00a0P4CLIENT; for example, on a UNIX system:<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

<\/a>$ P4CLIENT=bruno_ws ; export P4CLIENT<\/p>\n\n\n\n
 <\/p>\n

2.<\/td>\n

<\/a>Issue the\u00a0p4 client command.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

<\/a>Perforce displays the client specification form in your text editor.<\/p>\n\n\n\n
3.<\/td>\n<\/a>Specify (at least the minimum) settings and save the specification.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

<\/a>The minimum settings you must specify to configure a client workspace are:<\/p>\n\n\n\n
\u00a0<\/strong><\/p>\n

\u2022<\/strong><\/td>\n

<\/a>Workspace name<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

<\/a>The workspace name defaults to the client machine’s hostname, but a client machine\u00a0can contain multiple workspaces. To specify the effective workspace, set P4CLIENT.<\/p>\n\n\n\n
\u2022<\/strong><\/td>\n<\/a>Client root<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

<\/a>The client root is the top directory of your client workspace, where Perforce stores your\u00a0working copies of depot files. Be sure to set the client root, or you might inadvertently sync files to your client machine’s root directory.<\/p>\n

Note:<\/strong>
\nTo specify server settings on the command line, use the -p flag. For example:
\n<\/a>p4 -p localhost:1776 sync \/\/depot\/dev\/main\/jam\/Jambase<\/p>\n

<\/a><\/p>\n

Reference:<\/strong>
\nhttp:\/\/www.perforce.com\/perforce\/doc.current\/manuals\/p4guide\/02_config.html#1069873<\/strong><\/a>\u00a0<\/strong>
\nhttp:\/\/www.perforce.com\/perforce\/doc.current\/manuals\/p4guide\/02_config.html#1071378<\/strong><\/a>\u00a0<\/strong>
\nhttp:\/\/www.perforce.com\/perforce\/doc.current\/manuals\/p4guide\/01_install.html#1070774<\/strong><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

How to Setup p4 in Linux \/ Unix Well many people have these questions to me that they are facing issues setting up p4 client in Linux or Unix. The… <\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[370],"tags":[4503,373,4502,4501],"class_list":["post-4588","post","type-post","status-publish","format-standard","hentry","category-perforce","tag-how-to-setup-p4-in-linux-unix","tag-perforce","tag-perforce-setup-in-linux-unix","tag-setup-p4-in-linux-unix"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/4588","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=4588"}],"version-history":[{"count":2,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/4588\/revisions"}],"predecessor-version":[{"id":5423,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/4588\/revisions\/5423"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=4588"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=4588"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=4588"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}