[p4] mapping 1 area of depot to multiple areas of workspace

[Robert Cowham]

You have at least the following options:

1. Change the way you layout your release CD to structure differently, e.g.

- Common
- OS1
- OS2

Etc.

Before you throw your hands up in horror this is in fact what many, many
products do. 

2. Branch the files in Perforce (this can be done automatically using some
judicious scripting, e.g. have a Common location where you update and then
any change is automatically replicated to the "copies").

3. Create 1 workspace per OS which just maps out the appropriate things.
Very easy script to sync them all etc.

Robert

 

> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Edil Cadenas
> Sent: 11 October 2006 21:29
> To: Stephen Vance
> Cc: perforce-user at perforce.com
> Subject: Re: [p4] mapping 1 area of depot to multiple areas 
> of workspace
> 
> Hi Steve,
> 
> I'm trying to create release environments where each release 
> environment has its own workspace.  Thus, each workspace 
> (directory structure and
> all) reflects the actual Release CD.
> 
> The way the release is configured by our release/build team 
> is that certain files are shared by some modules.
> 
> e.g.
> 	Release CD
> 		- OS1
> 			- contains OS1-specific modules
> 			- contains Common Modules
> 		- OS2
> 			- contains OS2-specific modules
> 			- contains Common Modules
> 		- OS3
> 			- contains OS3-specific modules
> 			- contains Common Modules
> 		- OS4
> 			- contains OS4-specific modules
> 			- contains Common Modules
> 
> The Common Modules are of course stored in just one location 
> in the depot.
> 
> This is the kind of setup that we have in Visual SourceSafe 
> before.  And I'm just trying to duplicate the same setup in 
> Perforce for our release/build team.  In VSS, the Common 
> Modules are easily shared through links, which also holds 
> true for ClearCase.
> 
> But the absence of such feature in Perforce makes it 
> difficult to create such an environment.
> 
> Multiple workspaces won't work because each 
> workspace/environment represents an actual product (thus each 
> product has its own environment/workspace).  Having more than 
> one workspace for each product make it harder for our 
> release/build team to create timely releases as they would 
> need to handle several workspaces for each product.
> 
> 
> Best regards,
> Edil
> 
> -----Original Message-----
> From: Stephen Vance [mailto:steve at vance.com]
> Sent: Wednesday, October 11, 2006 1:01 PM
> To: Edil Cadenas
> Cc: perforce-user at perforce.com
> Subject: Re: [p4] mapping 1 area of depot to multiple areas 
> of workspace
> 
> Would multiple workspaces work for you? What are you really 
> trying to accomplish?
> 
> Steve
> 
> Edil Cadenas wrote:
> > Is it possible to map 1 area of the depot to several areas of the 
> > workspace?
> >
> > e.g.
> >
> >       //depot/dir1/...    //Workspace/local1/...
> >
> >       //depot/dir1/...    //Workspace/local2/...
> >
> >  
> >
> > I understand that the branch mechanism somehow provides a way to do
> that
> > but does it on the depot side.  What I would to do is to 
> just map the 
> > same are of the depot to several sections of my workspace.  I tried 
> > using the "+" mapping but I always end up getting the second line
> only.
> >
> >  
> >
> > Is what I'm trying to actually possible in Perforce?  Thanks for 
> > anyone's help.
> >
> >  
> >
> >  
> >
> > Best regards,
> >
> > Edil
> >
> >  
> >
> > _______________________________________________
> > perforce-user mailing list  -  perforce-user at perforce.com 
> > http://maillist.perforce.com/mailman/listinfo/perforce-user
> >
> >   
> 
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com 
> http://maillist.perforce.com/mailman/listinfo/perforce-user
> 
>