Andrew Smith wrote: >>> Would someone share why this may be happening and what I can do to avoid >>> it? >> >> You don't want to avoid it, otherwise your package would not have i18n >> support. >> > Yeah I meant avoid packaging them in the release tarball, I know they > have to be compiled before they're usable. The idea is not to force users to have msgfmt & co - all they need is the .mo files, because the code to access those files is typically included in the tarball's intl subdir. So as far as make dist is concerned, the gmo's are data files to be distributed; it's the maintainer's job to make sure they're up to date (via make update-po + getting the latest .po file from the translation project). >>> Also I just noticed a make clean doesn't delete the .gmo files. >> >> How about 'make distclean'? >> > Nope, still there. I have autoconf 2.61. Given they're part of the dist, that's expected. 'make maintainerclean' probably does clean them (but may require configuring with --enable-maintainer-mode or whatever the option is called). _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
