Opened 19 years ago
Last modified 16 years ago
#41 closed defect
Generate ChangeLog file with make dist — at Version 1
Reported by: | frae | Owned by: | frcm |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | ropp_io | Version: | 0.9 |
Keywords: | Cc: | axel.vonengeln@…, dave.offiler@… |
Description (last modified by )
I just included some modification to the ropp_io to automatically generate the ChangeLog file with a make dist command. This works as long as executed on the right linux box by looking for the svn2cl program. It also works if this program is not available. But it fails if the program is available but does not work correctly, e.g. svn is missing on another linux box.
Is there a way to avoid this so that make does not fall over if svn2cl fails? Or should one just assume that a program which is present should also work correctly.
The relevant modifications are visible in http://svn.marquardt.sc/cgi-bin/ropp.cgi/changeset/730, it is mainly a modification of the configure.ac to include:
AC_PATH_PROG(SVN2CL, svn2cl)
And a modification to the Makefile.am:
# 3. Generate the ChangeLog files automatically with make dist # ------------------------------------------------------------ dist-hook: if test -n "$(SVN2CL)"; then \ $(SVN2CL) --include-rev --group-by-day; \ fi;
If this is the correct way to persue this then I will make the necessary changes to the other modules. If not, please tell me what to modify or to just forget the whole issue.
Looks good to me, so if it works... (I haven't installed the svn2cl, so I can't check). Is there a way to clean the ChangeLog such that it does not hang around and gets accidentally checked in into the repository? One could make the file part of the files to be cleaned in the top level directory.
I think the ChangeLog generation would in effect fix #35, right? So I'll close that as a duplicate.