Yes, that is true. You would need to make the same change we had to make so
that your projects look for the shared file in a common location in the
project.
Rusty
-----Original Message-----
From: perforce-user-admin@xxxxxxxxxxxx
[mailto:perforce-user-admin@xxxxxxxxxxxx] On Behalf Of Grills, Jeff
Sent: Sunday, October 10, 2004 11:13 AM
To: Russell C. Jackson; Xianzhou Guo; perforce-user@xxxxxxxxxxxx
Subject: RE: [p4] Perforce limitation
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/...
j
-----Original Message-----
From: perforce-user-admin@xxxxxxxxxxxx
[mailto:perforce-user-admin@xxxxxxxxxxxx] On Behalf Of Russell C.
Jackson
Sent: Sunday, October 10, 2004 12:12 PM
To: 'Xianzhou Guo'; perforce-user@xxxxxxxxxxxx
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.
Rusty
-----Original Message-----
From: perforce-user-admin@xxxxxxxxxxxx
[mailto:perforce-user-admin@xxxxxxxxxxxx] On Behalf Of Xianzhou Guo
Sent: Sunday, October 10, 2004 9:18 AM
To: perforce-user@xxxxxxxxxxxx
Subject: [p4] Perforce limitation
Looks like perforce can not do fileshare as I did in VSS? Anybody got any
work around?
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com _______________________________________________
perforce-user mailing list - perforce-user@xxxxxxxxxxxx
http://maillist.perforce.com/mailman/listinfo/perforce-user
_______________________________________________
perforce-user mailing list - perforce-user@xxxxxxxxxxxx
http://maillist.perforce.com/mailman/listinfo/perforce-user
_______________________________________________
perforce-user mailing list - perforce-user@xxxxxxxxxxxx
http://maillist.perforce.com/mailman/listinfo/perforce-user
_______________________________________________
perforce-user mailing list - perforce-user@xxxxxxxxxxxx
http://maillist.perforce.com/mailman/listinfo/perforce-user
|
