[cvsnt] Re: Keyword Expansion Help

[Trevor Leybourne]

Thanks Tony and Glen (and Bo),

To explain a bit further, the files are Oracle and as such have a "property" 
concept within the binary file. The update is to a known property so the 
marker is always present and can easily be updated on each commit.

Because the system is comprised of over 600+ Oracle forms and 600+ Oracle 
reports, each of which is an independant file and can be run independantly, 
it is important that if an issue is raised in the system that we know 
exactly which version of the file the problem exists in. It is possible that 
while the customer is installing the system that one of the existing files 
would not get overwritten, or they may replace one of them with a different 
version (it has been known to happen).

Embedding the revision number, or the results of the $Id$ value into the 
file allows us to easily identify which tag or version the file is when a 
issue is reported and therefore easily be able to replicate it by checking 
out that exact version from CVS.

Bo has answered my thoughts with regards to CommitInfo or LogInfo. I have 
worked out that I cannot do it there. So I am wondering if it is possible 
with the Triggers and DLL's???

Is there any documentation on how these work? What data structures are 
supplied to the DLL at runtime or even better, is there an example C++ 
project for using the Triggers functionality?

Trevor

PS: The other issue I am aware of is that if two people check in, the 
version id will also cause a conflict. But I'm willing to live with that.

"Tony Hoyle" <tmh at nodomain.org> wrote in message 
news:d6a643$qbd$1 at paris.nodomain.org...
> Glen Starrett wrote:
>> Do you think the new DLL processing can do that?  I'm not sure, but I 
>> think it was much more flexible (precommit, etc.).  Maybe Tony can chime 
>> in.
>>
> It certainly makes it easier, but putting the *current* version number 
> into a file isn't going to work... the version number is calculated at the 
> same time that the deltas are calculated, so you can't modify the file 
> with that information.
>
> Using the date, author or commit identifier is a better bet, or perhaps a 
> user variable if there's a frontend process doing the committing.
>
> Tony