On Mon, 7 Aug 2000, Louis-David Mitterrand wrote:
> What is the best way to generate (and automatically update) a ChangeLog
> file from CVS commit log entries?
>
I have the ChangeLog updated when tags are initiated from the directory that
the ChangeLog exists. I've got perl code that automatically adds the username,
and date. Then the user enters a synopsis, and their editor is brought up so
that they can modify the ChangeLog accordingly. After the ChangeLog is updated
it checks it in, and e-mails a copy of the latest change to the initiating user.
Then said user can forward it out to others who want to know about the change.
You can have the ChangeLog updated when a commit happens, but then seperate
commits on different files for the same general change will be registered
each time. If you tag fairly often, it makes more sense to me to do it on the
tag.
I know emacs has a mode that makes it easy to deal with the standard version of
a ChangeLog. I use a modified version to archive more information that's critical
for our application.
Note, I just got these scripts working under client/server access. The design
of such scripts has to be different under client/server than local mode. The
only way I could see to get information from a remote user was to have X11 Widgets
pop up to get info. In my case we use "SSH" to come in to the CVS server so the
display can be set from the "SSH_CLIENT" variable. Also the user can make sure
their DISPLAY is set appropriately on the CVS server machine. Then I use some
simple Perl:Tk widgets to get the needed info.
Anyway, the point is, how you design your scripts depends on what access mode
will be used to access the repository.
Erik Kluzek, (CGD at NCAR)
National Center for Atmospheric Research
Boulder CO, (off) (303)497-1326 (fax) (303)497-1324
--------- Home page and public PGP key---------------
http://www.cgd.ucar.edu/~erik
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!