lilypond-devel
[Top][All Lists]
Advanced

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

Re: Making texi2html optional?


From: Graham Percival
Subject: Re: Making texi2html optional?
Date: Fri, 29 Aug 2008 14:32:41 +0100

+1.

I really want 2.12 to have the sexy new look.  Adding 500k (estimated)
to git for a few months is definitely worth it.

Cheers,
- Graham

On 8/29/08, Han-Wen Nienhuys <address@hidden> wrote:
> How large is texi2html?  Would it make sense to put the script into
> buildscripts/ until the correct version is released?
>
> On Fri, Aug 29, 2008 at 5:52 AM, John Mandereau
> <address@hidden> wrote:
>> Hi,
>>
>> I'm afraid we might wait a release of texi2html for a while (several
>> weeks).  We can't require texi2html in Lily 2.12 if it hasn't been
>> officially released; OTOH Reinhold has put a lot of effort into using
>> texi2html for building our docs, so we really should release 2.12. HTML
>> documentation compiled with texi2html, and thus one or two 2.11.x
>> releases for testing.  That's why I suggest to make texi2html optional
>> in configure script, and write conditional make rules for building HTML
>> docs -- the rules would be defined conditionnally like
>>
>> ifeq (,$(findstring texi2html,$(MISSING_OPTIONAL)))
>> # rules using texi2html
>> else
>> # rules using makeinfo
>> endif
>>
>> Then we could immediately merge dev/texi2html into master.  I can
>> provide a patch prior to pushing if you like, but I think it's not too
>> much of a burden: only texinfo-rules.make and doc-i18n-user-rules.make
>> would be affected besides configure.in.
>>
>> Cheers,
>> John
>>
>>
>>
>> _______________________________________________
>> lilypond-devel mailing list
>> address@hidden
>> http://lists.gnu.org/mailman/listinfo/lilypond-devel
>>
>
>
>
> --
> Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen
>
>
> _______________________________________________
> lilypond-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/lilypond-devel
>




reply via email to

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