[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: What's the deal with the module system?

From: John Mandereau
Subject: Re: What's the deal with the module system?
Date: Wed, 25 Nov 2009 11:58:17 +0100

Le mercredi 25 novembre 2009 à 11:41 +0100, David Kastrup a écrit :
> When the code requires meddling with the internals of Texi2HTML, like I
> understood Reinhold, it is in some parts linked to the particular
> version.  In this case it makes sense to distribute the required version
> alongside since no other version can be known to work, anyway.

These are not internals, but a customization interface that is part of
the design of Texi2HTML.  Texi2HTML is going to replace Makeinfo real
soon now, that might one of the reasons why this interface changed in

> Optional Makefile targets for downloading and compiling a particular
> version in-tree when configure finds that the current one will not work?
> Or any configure or error messages or error catching that will give a
> useful information linking this failure of the test suite with the
> Texi2HTML version?
> Or Makefile targets (and reference to them in configure/error messages)
> which don't produce the HTML information and thus don't fail when
> Texi2HTML is not of the right version?

Your suggestions are perfectly right.  However, we plan to replace
current build system, so we're not going to refine configure checks.  If
you call "make help", you'll see that "make doc-stage-1" does compile
documentation in all formats but HTML.


Attachment: signature.asc
Description: Ceci est une partie de message numériquement signée

reply via email to

[Prev in Thread] Current Thread [Next in Thread]