first, this is listed in DEPEND, not RDEPEND ... i dont see how fontforge could be needed at build but not runtime ...
more to the point, this atom causes obvious problems now that we have fontforge-20070501 in the tree
(In reply to comment #0)
> first, this is listed in DEPEND, not RDEPEND ... i dont see how fontforge could
> be needed at build but not runtime ...
That is straight from their own docs. I imagine it is used for building the music fonts. See http://lilypond.org/doc/v2.10/Documentation/topdocs/INSTALL#Top
> more to the point, this atom causes obvious problems now that we have
> fontforge-20070501 in the tree
The atom is there _because_ that new fontforge is in the tree. Lilypond doesn't like it.
then fix lilypond
users are getting screwed here with upgrade/downgrade loops
Created attachment 119482 [details, diff]
This is the patch I'm using to get lilypond to build with latest fontforge (20070501). I haven't submitted it anywhere yet (too lazy/wanted to get some testing in first) but I think it does the right thing; lilypond seems to work.
I incorporated this patch in the ebuild and it worked fine for me.
Created attachment 119533 [details]
ebuild with Ed Catmur's patch
I have not tested if it work with older fontforge versions, so maybe at a change in the DEPEND section is needed, but it work fine with 20070501.
Upstream have applied the patch. It will be included in 2.10.26.
I've committed the patch to the tree to avoid cyclic dependencies between mftrace and lilypond about fontforge.