Hi Simon,
> > + When you run @code{gettextize}, always use the @code{gettextize} from the
> > + newest GNU gettext release found on @url{http://ftp.gnu.org/gnu/gettext/},
> > + and invoke @code{gnulib-tool} afterwards.
>
> That doesn't work for me currently -- I don't assume developers have
> gnulib installed. Instead I store the gnulib-tool --import'ed files in
> git. This has worked fine for a long time. Do we want to officially
> abandon this way of using gnulib?
Of course your way of doing is fine. I simply had forgotten about this
situation when I wrote the text.
Applied the tweak below.
> Alternatively, I could document the work-around I use to solve the
> gettext vs gnulib vs autoconf problem right now: store all gnulib
> generated files in git, and before running autoreconf move the gnulib
> copy of config.rpath out of the way, and after running autoreconf, move
> it back again.
It's simpler to document it by saying to rerun gnulib-tool afterwards.
Otherwise we have also to document _which_ files conflict; and this set
of files changes over time. Today it's only */*.m4 and build-aux/config.rpath;
tomorrow it could also be build-aux/config.libpath or some other files.
Bruno
2008-03-25 Bruno Haible <[EMAIL PROTECTED]>
* doc/gnulib-tool.texi (gettextize and autopoint): Explain in more
detail which gettext release to use.
Reported by Simon Josefsson.
*** doc/gnulib-tool.texi.orig 2008-03-26 03:01:46.000000000 +0100
--- doc/gnulib-tool.texi 2008-03-26 03:01:16.000000000 +0100
***************
*** 400,407 ****
@enumerate
@item
When you run @code{gettextize}, always use the @code{gettextize} from the
! newest GNU gettext release found on @url{http://ftp.gnu.org/gnu/gettext/},
! and invoke @code{gnulib-tool} afterwards.
@item
When a script of yours run @code{autopoint}, invoke @code{gnulib-tool}
--- 400,410 ----
@enumerate
@item
When you run @code{gettextize}, always use the @code{gettextize} from the
! matching GNU gettext release. For the most recent Gnulib checkout, this is
! the newest release found on @url{http://ftp.gnu.org/gnu/gettext/}. For an
! older Gnulib snapshot, it is the release that was the most recent release
! at the time the Gnulib snapshot was taken. Then, after @code{gettextize},
! invoke @code{gnulib-tool}.
@item
When a script of yours run @code{autopoint}, invoke @code{gnulib-tool}
