Simon Josefsson via Gnulib discussion list writes:
>>> What do you think about this change?
>>>
>>> - AUTORECONFFLAGS="--verbose --install --force -I $m4_base $ACLOCAL_FLAGS"
>>> + AUTORECONFFLAGS="--verbose --install --force $ACLOCAL_FLAGS"
>>
>> It sounds like 'autoreconf' does a better job at
Bruno Haible via Gnulib discussion list writes:
> Simon Josefsson wrote:
>> If the diff is unreadable, the summary is that it just moves around
>> things.
>> ...
>> The problem happens because 'make release' invoke (via GNUmakefile
>> '_version' target) autoreconf to re-generate files for the new
Simon Josefsson wrote:
> If the diff is unreadable, the summary is that it just moves around
> things.
> ...
> The problem happens because 'make release' invoke (via GNUmakefile
> '_version' target) autoreconf to re-generate files for the new version
> number. I believe this step is working fine,
All,
I've noticed that 'make dist' tarballs can be different from 'make
release' tarballs with gnulib, the difference is in aclocal.m4 and
Makefile.in:
│ ├── libidn2-2.3.8/aclocal.m4
│ │ @@ -1198,33 +1198,14 @@
│ │ m4_include([unistring/m4/unictype_h.m4])
│ │ m4_include([unistring/m4/uninorm_h.
