Re: a new lilypond build failure

[Thomas Bushnell BSG]

Jan Nieuwenhuizen <address@hidden> writes:

> Thomas Bushnell writes:
>
>> But now there's a new, more subtle, one.
>
> Fixed in CVS, see patch below.
>
> Thanks for the report (and sorry that this kludge survived in the
> first place).

Ah, I like.  Many thanks.

My patch was worse (to have an environment variable that, if set,
forces running-from-gui? to return #f).  I like this one more. :)

Anyway, with my patch (or equivalently with yours, I'm sure), lilypond
2.6.3 is now in Debian.  (Whew!)

It took overcoming an mftrace bug or two, getting Debian's fontforge
up-to-date (which required overcoming some other bugs!), finding and
fixing the running-from-gui? kludge, and a whole host of other stuff.

And, during the whole process, 2.6.4 got released... :)

I'm going to start going through the many Debian bug reports filed
against the Debian lilypond package now, many of which are very old
and were reported against version 2.2 or older.  I expect they are
nearly all no longer real bugs.  Then I'll upgrade to 2.6.4 or
whatever is the latest on the branch.

Lilypond is such a great thing, I'm glad that finally Debian users
will have an up-to-date package at least in Debian unstable.

Oh, and a request: the debian/ directory in the tarballs that you all
distribute isn't very helpful to me, because I have a separate way of
keeping track of what goes in there.  It would suit me fine if it
simply went away entirely; I'm not using it in my packages, and it may
easily be confusing to others.

Thomas