The Go programming environments, like Java and C#, have their own way of
invoking the Go compiler. It's not entirely trivial. Therefore here is
a module to do that in a simple way. Similar to 'javacomp-script' and
'csharpcomp-script'.
2025-03-06 Bruno Haible
gocomp-script: New module.
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,
Hi Simon,
> I'm finally testing this, now that gnulib-l10n is in Debian and libidn2
> is coming closer to a release that could make use of it. I'm happy to
> say it is working! This is a nice improvement, it gets the version-etc
> translations from the gnulib domain:
>
> jas@kaka:~/src/libidn2$
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.
