lilypond-devel
[Top][All Lists]
Advanced

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

Re: The catastrophe has arrived.


From: David Kastrup
Subject: Re: The catastrophe has arrived.
Date: Wed, 23 Oct 2013 19:38:30 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

James <address@hidden> writes:

> On 23/10/13 18:12, David Kastrup wrote:
>>
>> Should we create a release of 2.16.3 which only differs from 2.16.2 in
>> cherry-picking the autoconf change making it refuse to compile with
>> buggy versions of Metapost?
>>
> Well personally I think we should 'warn' than refuse to compile. Those
> that know how to 'go back' to an earlier version of metapost will,
> those that don't will not then be stuck with something that doesn't
> work.
>
> If you see what I mean.

I see what you mean, but we are not talking about cosmetic differences
here.  We are talking about fatally broken output.  It's not just every
treble clef that looks like something the cat dragged in, but also all
the flags are missing pieces of their spine.

This is not something that a warning is appropriate for.  People who
want to continue compiling with that setup _really_ need to hand-edit
the configuration test in order to _insist_ getting a broken version of
LilyPond.

-- 
David Kastrup



reply via email to

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