14 messages in com.perforce.perforce-user[p4] VSS-like "Links" in Perfoce?| From | Sent On | Attachments |
|---|---|---|
| Tim Henrion | 18 Sep 2000 05:40 | |
| Steve Bennett | 18 Sep 2000 07:29 | |
| Jeff A. Bowles | 18 Sep 2000 10:13 | |
| Jeff A. Bowles | 18 Sep 2000 10:44 | |
| Russell Jackson | 18 Sep 2000 10:50 | |
| Jeff A. Bowles | 18 Sep 2000 10:58 | |
| Tim Henrion | 18 Sep 2000 13:19 | |
| Steve Bennett | 18 Sep 2000 13:59 | |
| Russell Jackson | 18 Sep 2000 14:08 | |
| Richard Brooksby | 18 Sep 2000 14:09 | |
| Steve Bennett | 18 Sep 2000 14:09 | |
| George Van Treeck | 18 Sep 2000 21:45 | |
| Berend de Boer | 19 Sep 2000 13:46 | |
| Richard Brooksby | 19 Sep 2000 14:26 |
| Subject: | [p4] VSS-like "Links" in Perfoce? |
|---|---|
| From: | Russell Jackson (rjac...@symantec.com) |
| Date: | 09/18/2000 10:50:53 AM |
| List: | com.perforce.perforce-user |
To add to this thread:
I loath that feature of VSS. I once received a copy of someone's source who had been using VSS, and it had over 500 copies of the same file scattered throughout the source tree. It was a nightmare to clean up.
The better way to share a common file among projects is to keep one, and only one copy of that file in Perforce, and then pull that file into your project using a client view. Then use relative paths or the include environment variable within your build enviroment to include that file in the projects that need it.
Rusty
Russell C. Jackson CM Manager Symantec Corporation 310-449-4182
Additional contact information: CM on call phone, available 24x7: 6-310-5444
909-212-0636 cell phone rcjackson at alum.atu.edu - home email
"Jeff A. Bowles" <jab at pobox.com>@perforce.com on 09/18/2000 10:13:46 AM
Sent by: perforce-user-admin at perforce.com
To: Tim Henrion <Tim at highpoint.com> cc: "'perforce-user at perforce.com'" <perforce-user at perforce.com> Subject: Re: [p4] VSS-like "Links" in Perfoce?
At 08:41 AM 9/18/2000 -0400, Tim Henrion wrote:
Does anyone have a good method for duplicating Visual SourceSafe "links" in Perforce? I'd like to have links to global include files exist in multiple directories in my depot. All of the links essentially point to the same file. Whenever someone checks out/changes/checks in the file via any of the links, all links to the file automatically get updated to the new
contents.
Look at the following scripts in the public.perforce.com:1666 depot: //guest/jeff_bowles/scripts/p4push.dat //guest/jeff_bowles/scripts/p4push.pl These implement the model that you can have a ``master copy'' of a file that gets updated, and propogates the changes to another set of files. The model is that one file changes, the rest are downstream copies that get updated as the result of an integrate.
You would just run this from crontab(1) or "at" or perhaps a "p4 review" script. And you might use "p4 protect" to forbid subordinate copies from being directly updated/edited.
Don't infer that I like this model: a couple of users asked me for this. I think that updating a file in location A and having three files in locations (B,C,D) get updated is poor form: the Perforce model is far more of the "you only update that which you mean to, and you do it explicitly."
So, use this as a stop-gap measure and then change your procedures.
-jab
_______________________________________________ perforce-user mailing list - perforce-user at perforce.com http://maillist.perforce.com/mailman/listinfo/perforce-user