Eric Blake wrote: > gnulib-tool output is already verbose It was mentioned that verbosity can be overcome by looking at the differences between the previous run and the current run. I use the attached script daily.
> is there a better way to just automatically update po/Makevars (possibly > by teaching po/Makevars how to include a second file)? Not so far. But what I could do in the next gettext release is to use the configure script as a collector for all the needed options: I could define a macro AM_XGETTEXT_OPTION([option]) that would augment an AC_SUBSTed variable which then gets used in po/Makefile, together with the XGETTEXT_OPTIONS from po/Makevars. How does that sound? > > Notice from module error: > > If you are using GNU gettext, add the following options to > > XGETTEXT_OPTIONS > > in your po/Makevars: --flag=error:3:c-format > > --flag=error_at_line:5:c-format > > Why error, but not also verror? Forgot about it. Of course, 'verror' should be handled like 'error'. Bruno
rerun
Description: application/shellscript
