Hi Andy,
> Question, do you think it would be reasonable for autopoint to avoid
> overwriting newer files? It seems like the sort of problem we could
> avoid, but who knows.
Such a solution would be
- partly ineffective, because Gnulib has only recently started to use
'# serial ...' annota
Hi Bruno!
Thanks for your kind answer and tips :)
On Mon 24 Jun 2024 19:09, Bruno Haible writes:
> I can reproduce a problem by
> 0. using a git checkout of guile ('main' branch, not 'master' branch),
> 1. using a GNU gettext version 0.22.5, 0.21, 0.20.2, or 0.19.8.1,
> 2. removing the gn
Hi Andy,
Thanks for CCing me. You could equally well have CCed bug-gnulib; that
works too.
> To recap, gnulib provides compile-time shims for "foreign" or
> out-of-date target systems that allows Guile to program to a single
> POSIX + GNU API and not worry too much about what the system actually
Maxime Devos writes:
>>To wit, running "autoreconf -vif" invokes the "autopoint" tool supplied
> by installed gettext, which copies over .m4 files from installed
> gettext, but [problems]
>> [...]
> > 6. Something else? Stop using gnulib?
>
> Maybe make a shell no-op shell script in
> “insert-
>To wit, running "autoreconf -vif" invokes the "autopoint" tool supplied
by installed gettext, which copies over .m4 files from installed
gettext, but [problems]
> [...]
> 6. Something else? Stop using gnulib?
Maybe make a shell no-op shell script in “insert-directory-name-here/autopoint”
and a
