Bug 178629 - media-sound/lilypond has broken fontforge atoms in DEPEND
|
Bug#:
178629
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: All
|
Status: RESOLVED
|
Severity: major
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: scheme@gentoo.org
|
Reported By: vapier@gentoo.org
|
|
Component: Applications
|
|
|
URL:
|
|
Summary: media-sound/lilypond has broken fontforge atoms in DEPEND
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2007-05-15 12:59 0000
|
<=media-gfx/fontforge-20070312
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)
> <=media-gfx/fontforge-20070312
>
> 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 an attachment (id=119482) [details]
fontforge-RemoveATT.patch
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.
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.
