[p4] Creating and managing empty folders...

Melissa mkacher at msn.com
Mon Nov 13 19:07:39 PST 2006

Let's say you are using make. From what you describe, one of you actions
requires a folder. So to me, it sounds like that target needs to depend on
the folder. You should have a rule for that folder. It's action would create
the folder if it doesn't exist.

The advantage of this is that your builds always work, no matter what
version control system you use. You build will still work even if the code
is taken out of context (out of the version control system.)

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Jeff Nemecek
Sent: Monday, November 13, 2006 3:32 PM
To: perforce-user at perforce.com
Subject: [p4] Creating and managing empty folders...

So, given a situation where you need to create a stable, consistent folder
structure for a project, how do you approach the issue of empty folder
creation in Perforce?  Subversion, CVS and unmentionable source control
systems have solutions for this.  I am not familiar with the best way to
resolve this using Perforce.

Do you use token files to populate each folder you need to create?  Do you
use external tools to drive folder creation of templated projects? Do you
create folders in the file system and not worry about loading them into
Perforce until files exist underneath them?

I'm interested in any and all approaches or alternatives that you may have
to this issue.


Jeff Nemecek
Lead Engineer, Corporate Software Development
aQuantive, Inc
Leading Businesses in Digital Marketing

perforce-user mailing list  -  perforce-user at perforce.com

More information about the perforce-user mailing list