[EMAIL PROTECTED] on 05/22/2000 04:22:01 PM
>We have some files that are correctly added into the repository and
>that are needed for "compilation" purposes (actually it's a conversion
>step where I'm converting files from DocBook SGML to groff, LaTeX and
>other markup languages). They are part of the project and need to be
>there.
>
>The tool that generates this file modifies it's contents adding a
>timestamp line (or changing the exsting one). I want to check it out
>and commit all the other files but I want to keep this one out of CVS
>commits except when explicitly stated (or, if it isn't possible, I can
>change it directly on the repository...).
>
>I can't prevent these lines from being modified and I can't deliver my
>project without this file. That's my problem.
I see a few things you can do (none are elegant):
1. Don't regenerate the file. If nothing that the file depends on has changed,
why regenerate it?
2. Strip out the timestamp (possibly replacing it with something generic) before
doing commits. This may break the application when it goes to read the file.
3. Complain to the vendor. Vendors should know better than to put variable
meta-information (like timestamps) inside files with real content. What are the
timestamps used for? Can't the application use the file's mod time? Can the
application place this info somewhere else?
Noel
This communication is for informational purposes only. It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.
