[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: libidn2: ChangeLog, bootstrap

From: Tim Ruehsen
Subject: Re: libidn2: ChangeLog, bootstrap
Date: Wed, 28 Dec 2016 15:19:33 +0100
User-agent: KMail/5.2.3 (Linux/4.8.0-2-amd64; KDE/5.28.0; x86_64; ; )

On Wednesday, December 28, 2016 3:02:55 PM CET Simon Josefsson wrote:
> Tim Ruehsen <address@hidden> writes:
> > Hi Simon,
> > 
> > You recently removed the ChangeLog and added a hook into bootstrap.
> > 
> > I just want to mention how wget is doing this:
> > - renamed ChangeLog to ChangeLog-2014-12-10
> > - added a dist-hook rule into which creates a ChangeLog when
> > needed (make dist) by merging ChangeLog-2014-12-10 with the new git
> > commit messages.
> > 
> > This allows creating a ChangeLog from git without another external tool -
> > just
> > with the scripts from gnulib:
> Thanks for the hint -- see for how it is done in libidn2, i.e.:
> ChangeLog:
>       git2cl > ChangeLog
> tarball:
>       ! git tag -l $(PACKAGE)-$(VERSION) | grep $(PACKAGE) > /dev/null
>       $(MAKE) ChangeLog distcheck
> The idea is that on 'make release', the ChangeLog is re-generated from
> git commit logs and will be included in the tarball.  This broke because
> ChangeLog had been accidentally been committed at some point.

The wget method has the advantage that you don't have to remember 'make 
release', it is regenerated automatically when you create the tarball (make 
dist, make distcheck).
Another advantage is that wget doesn't need get2cl - which might not be 
available on e.g. Solaris.
E.g. 'gengetopt' is not available there and it was not possible for me to 
built it (some auto* stuff was not compatible). That means I can't build 
libidn2 there at the moment. IMO, such dependencies are a waste of time since 
they just solve trivial tasks, basically nothing.

Maybe it is possible to use gnulib's git-to-changelog instead of git2cl ?

Regards, Tim

Attachment: signature.asc
Description: This is a digitally signed message part.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]