Re: a new lilypond build failure

[Thomas Bushnell BSG]

Jan Nieuwenhuizen <address@hidden> writes:

> LilyPond no longer uses
>
>     ec-fonts-mftraced

Wait, you mean showed up and is now gone?  What's it for anymore?  Why
did we ever have it? :)

> I think the package
>
>     musixtex-fonts
>
> does not exist and if it does, I cannot imagine any conflicts.  

The Debian package no longer includes this conflict.

> Also,
> as LilyPond does not use tex by default
>
>     libkpathsea3
>     tetex-bin
>     tetex-extra
>
> are not requirement anymore.  They may be useful, and are required
> when using the (unsupported) TeX backend.

Ok; they were once used for processing the texinfo docs, right?

You say that the TeX backend is no longer supported (!).  Why is this?
The manual still regards .tex output as the default output format and
plenty of users regard it as the expected thing.

>> 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.
>
> Thanks!  Yes, that's great.  And don't forget the Ubuntu users.

Well, I can't support everyone.  Ubuntu can copy Debian, but I can't
simultaneously handle that.

>> Oh, and a request: the debian/ directory in the tarballs that you all
>> distribute isn't very helpful to me
>
> I always liked to distribute this for users to build their own deb
> package [from CVS].  What do you think?

Well, it's a dangerous thing.  Among other things, their version
numbers might collide badly with the official Debian ones.  Best it
should have different package names to prevent this sort of thing from
happening.


Thomas