[p4] Perforce limitation - Noel Yap - com.perforce.perforce-user

7 messages in com.perforce.perforce-user[p4] Perforce limitation

From	Sent On	Attachments
Xianzhou Guo	10 Oct 2004 09:17
Russell C. Jackson	10 Oct 2004 10:11
Grills, Jeff	10 Oct 2004 10:11
Grills, Jeff	10 Oct 2004 11:12
Russell C. Jackson	10 Oct 2004 21:23
Noel Yap	11 Oct 2004 05:46
Matthew Janulewicz	11 Oct 2004 09:56

Subject:	[p4] Perforce limitation
From:	Noel Yap (Noel...@morganstanley.com)
Date:	10/11/2004 05:46:15 AM
List:	com.perforce.perforce-user

IMO, the best way to do something like this is to release the shared stuff as a
separate project into a known location and treat it as a third party entity.

For example, do you share the C libraries? What about other libraries? Why not
treat whatever you want to share like these?

HTH, Noel

Grills, Jeff wrote:

A perforce client can't map a single file to multiple locations, though.

I have seen some projects where do something like this in a client to get a copy of the engine in their project:

//depot/project/src/project/... //client/project/src/project/... //depot/engine/src/engine/... //client/project/src/engine/...

I still think this is a bad plan because people working in the engine can break the project build because they're not (or shouldn't be) responsible for testing a specific project build. The second line should instead be a branch like so, with integrations happening at an appropriate rate:

//depot/engine/src/engine/... //depot/project/src/engine/...

-----Original Message----- From: perforce-user-admin at perforce.com [mailto:perforce-user-admin at perforce.com] On Behalf Of Russell C. Jackson Sent: Sunday, October 10, 2004 12:12 PM To: 'Xianzhou Guo'; perforce-user at perforce.com Subject: RE: [p4] Perforce limitation

You use the clientspecs in Perforce to pull the fileset you want from Perforce rather than creating shares. IT seems like more work, but in reality, it is much safer and better. We had one instance of taking over a source base from a company that had a shared a file over 500 times. They gave us a source drop or their code, and of course it contained 500 copies of the same file. We wasted a lot of time cleaning that up so that the references in all the projects pointed to a single copy of that file just so that we could start working on the project.

File shares in VSS are not a good thing even though they appear to be.

-----Original Message----- From: perforce-user-admin at perforce.com [mailto:perforce-user-admin at perforce.com] On Behalf Of Xianzhou Guo Sent: Sunday, October 10, 2004 9:18 AM To: perforce-user at perforce.com Subject: [p4] Perforce limitation

Looks like perforce can not do fileshare as I did in VSS? Anybody got any work around?