14 messages in com.perforce.perforce-user[p4] cascading file update| From | Sent On | Attachments |
|---|---|---|
| Frederic Barachant (ST) | 09 Feb 2004 08:53 | |
| Noel Yap | 09 Feb 2004 09:06 | |
| Frederic Barachant (ST) | 11 Feb 2004 00:16 | |
| Oren Shemesh | 11 Feb 2004 01:41 | |
| Frederic Barachant (ST) | 11 Feb 2004 07:59 | |
| Oren Shemesh | 11 Feb 2004 08:16 | |
| Frederic Barachant (ST) | 11 Feb 2004 08:21 | |
| Chuck Karish | 11 Feb 2004 10:08 | |
| ouch...@telus.net | 19 Feb 2004 11:50 | |
| Janulewicz, Matthew | 19 Feb 2004 11:58 | |
| Doug Palmer | 19 Feb 2004 12:00 | |
| Jim Crossley | 19 Feb 2004 12:05 | |
| ouch...@telus.net | 19 Feb 2004 12:11 | |
| Ed Mack | 19 Feb 2004 12:51 |
| Subject: | [p4] cascading file update![]() |
|---|---|
| From: | Frederic Barachant (ST) (fbar...@corys.fr) |
| Date: | 02/11/2004 12:16:02 AM |
| List: | com.perforce.perforce-user |
Hello. The reason is that the repository was installed to be a valid image of a complete dev trunk. The generated files are used during dev, thus needed to be stored and retrieved the same way as others. To simplify (this is not our case, but quite similar and i'm interested in the answer), if you had antlr generated classes, how would you do to ensure that the .g and classes are consistent in the repository? Thanks a lot.
Noel Yap wrote:
What's the rationale for storing generated files?
Noel
"Frederic Barachant (ST)" wrote:
Hello. Here is the context: Some files of our repository are script generated, based on the content of the repository itself. Ideally, when some files are sent to the repository, some others, generated by the scripts should also be sent.
One of the ways to go would be to modify the generation scripts to also send the new data to the repository. That implies listing the content of the repository, generating the scripted files, and sending it to the repository in the same batch. I don't like that eventuality, because it makes scripts quite long to program and forces some of our users to use special scripts to handle some types of files.
One other would be to start the generation of the files from perforce when some certain files are triggered for update, and do the whole stuff directly by the server on a user action. i would prefer that road because user has only on thing to do, same for all file types and we handle the things in the background.
Are there other ways to handle storage of generated files? How do you generally do that? What do you think of the solutions i'm planning? Thanks for sharing any experience you might have with that problem.
_______________________________________________ perforce-user mailing list - perforce-user at perforce.com http://maillist.perforce.com/mailman/listinfo/perforce-user




