[p4] How many of you use a sandbox area for user items.

Brian Colfer briancolfer at comcast.net
Tue May 9 00:42:37 PDT 2006


I've been at companies where sandboxes are standard and I've set this
practice up a few times.  I think it's a great idea but wanted to see how
much of a "Best Practice" it is.

Slava,  I don't understand how your response addresses my question.  Are you
saying that you check in your build products into a perforce depot? It seems
that you are referencing a workspace directory... I don't get it.



-----Original Message-----
From: Slava Imeshev [mailto:imeshev at yahoo.com] 
Sent: Monday, May 08, 2006 7:54 PM
To: Brian Colfer; perforce-user at perforce.com
Subject: Re: [p4] How many of you use a sandbox area for user items.

----- Original Message ----- 
From: "Brian Colfer" <briancolfer at comcast.net>
To: <perforce-user at perforce.com>
Sent: Monday, May 08, 2006 6:16 PM
Subject: [p4] How many of you use a sandbox area for user items.


> List,   do you use a sandbox ... or other area defined for user specific
> items?  
> 
> That is besides ... you Stephen P. 

Generally we recommend our customers to limit items that 
are not a part of the depot view to the build results stored under 
a single directory. Such directory is called temp usually.

This allows to clean up such directory at a single shot as a part
of the build process, something along the 

  make clean 

lines.

The directory structure under the root of the client spec aka workplace 
usually looks as the following if this approach is followed:

./3rdparty
./src
./bin
./doc
./temp

This way those "user-specific" items are contained to the temp dir
and don't intersect with normal operations on the workplace.

Regards,

Slava Imeshev





More information about the perforce-user mailing list