[p4] newbie questions

Stephen Vance steve at vance.com
Thu Jul 13 16:42:01 PDT 2006

You're on the right track. The 'p4 client sandbox' command *defines* the 
client, meaning where you want it (Root) and how that location maps to 
the server (View). You don't need to create or be in the directory that 
is your root. Perforce will do that for you. Your next step is 'p4 sync' 
which will give you read-only copies of your source. Then you'll do 'p4 
edit', 'p4 add', 'p4 delete', and so forth.

I'd recommend going through the Perforce User's Guide. It gives you some 
step-by-step scenarios to get familiar with Perforce.


Mike wrote:
> Here's my paranoia running rampent again.
> I've used cvs and rcs a lot, no problems there.
> The new job uses perforce. I want to create a
> 'sandbox' for testing checking things in, out,
> adding, deleting, etc. I think this is a new client
> or workspace.
> I'm worried about deleting the wrong things.
> I'm using cygwin and the p4.exe command works.
> Eventually these commands will run in unix servers
> and some windows servers under cygwin.
> What I'm thinking is:
> $ set | grep P4
> P4CLIENT=sandbox
> P4EDITOR=/usr/bin/vi
> P4PORT=perforce:1666
> P4USER=systems
> $ which p4
> /usr/local/bin/p4
> $ p4 client sandbox
> (this creates the 'client' yes?)
> (here I would do a 'cd sandbox', 'cvs import sandbox begin start',
>   'cd ..', 'mv sandbox sandbox.orig', 'cvs co sandbox')
> (how do I get the 'client' as a subdirectory?)
> How much pain am I going to have when I'm done and
> execute 'p4 client -d sandbox'?
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user

More information about the perforce-user mailing list