Re: [PATCH 1/2] build: Use an up to date copy of texinfo.tex

[Mathieu Lirzin <mthl@gnu.org>]

John Darrington <john@darrington.wattle.id.au> writes:

> On Fri, Feb 24, 2017 at 08:25:20PM +0100, Mathieu Lirzin wrote:
>      
>      John Darrington <jmd@gnu.org> writes:
>      
>      > * build-aux/texinfo.tex,ref: New file, copied from texlive-minimal
>      > * bootstrap: Use it, if newer than the texinfo.tex from automake.
>      > ---
>      >  bootstrap                 |    11 +-
>      >  build-aux/texinfo.tex,ref | 11562 ++++++++++++++++++++++++++++++++++++++++++++
>      >  2 files changed, 11572 insertions(+), 1 deletion(-)
>      >  create mode 100644 build-aux/texinfo.tex,ref
>      >
>      
>      Do you know why building Guix manual fails to build with older
>      "texinfo.tex"?
>
>      If this related to some special texinfo syntax used in Guix manual?
>
> Yes.  It's the use of @inlinefmtifelse command. (perhaps other commands too).

There is only one instance of this command which is in "doc/guix.texi":

  If you are instead planning to encrypt the root partition, you can use
  the Cryptsetup/LUKS utilities to do that (see @inlinefmtifelse{html,
  @uref{https://linux.die.net/man/8/cryptsetup, @code{man cryptsetup}},
  @code{man cryptsetup}} for more information.)

I have tested that without it, 'make pdf' succeeds.  IMHO the manual
would be fine without this feature.  As a consequence --to avoid adding
complexity to the build process-- I would be in favour of not using
@inlinefmtifelse until Automake distributes a compatible version in its
current version.

>      What about checking in texinfo.tex and removing the -f (--force) option
>      when invoking 'autoreconf'?  This would ensure that texinfo.tex is not
>      overwritten.
>
>
> I guess it might work.  But I haven't tried it.

Thank you for the debugging information.  :)

-- 
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37