D'Arcy J.M. Cain wrote:
> On Wed, 28 Feb 2007 09:49:35 +0100
> Joerg Sonnenberger <joerg@britannica.bec.de> wrote:
> 
>>On Wed, Feb 28, 2007 at 02:59:33AM -0500, D'Arcy J.M. Cain wrote:
>>
>>>>I think this broke fonts/ec-fonts-mftraced. Can you please investigate?
>>>
>>>The only thing that seems to depend on it is lilypond and that's been
>>>broken for ages.  I am currently trying to upgrade lilypond and it does
>>>not seem to require it any more.  Do you know of anything else that
>>>uses this?  It is no longer supported it seems.
>>
>>lilypond and ec-fonts-mftraced, that's all.
> 
> 
> Well, I think we should just drop ec-fonts-mftraced and update lilypond
> to 2.10.0.  The only problem is that so far I can make it build but it
> fails on installation.  I think I should commit anyway.  There is no
> point fixing an old version of the software.  We may as well have a new
> version that doesn't work instead.  In fact, what I have now is a step
> ahead because at least it builds.

but lilypond *did* build for me as recently as 2 weeks ago


# ls -l packages/All/lilypond-2.4.6.tgz
-rw-r--r--  1 root  wheel  2969515 Feb 13 01:04 
packages/All/lilypond-2.4.6.tgz


so no, a new package thats broken is not better!  Are you sure there 
wasn't something else broken on your system?


-Dan