Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 178629
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Scheme Herd <scheme@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: SpanKY <vapier@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
fontforge-RemoveATT.patch fontforge-RemoveATT.patch patch Ed Catmur 2007-05-16 21:39 0000 348 bytes Details | Diff
lilypond-2.10.23-r1.ebuild ebuild with Ed Catmur's patch text/plain Dominique Michel 2007-05-17 14:28 0000 2.76 KB Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 178629 depends on: Show dependency tree
Bug 178629 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   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

------- Comment #1 From Marijn Schouten 2007-05-15 13:15:25 0000 ------- 
(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.

------- Comment #2 From SpanKY 2007-05-15 14:58:34 0000 ------- 
then fix lilypond

users are getting screwed here with upgrade/downgrade loops

------- Comment #3 From Ed Catmur 2007-05-16 21:39:19 0000 ------- 
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.

------- Comment #4 From Dominique Michel 2007-05-17 14:26:35 0000 ------- 
I incorporated this patch in the ebuild and it worked fine for me.

------- Comment #5 From Dominique Michel 2007-05-17 14:28:44 0000 ------- 
Created an attachment (id=119533) [details]
ebuild with Ed Catmur's patch

------- Comment #6 From Dominique Michel 2007-05-17 14:31:47 0000 ------- 
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.

------- Comment #7 From Marijn Schouten 2007-06-02 11:14:13 0000 ------- 
Upstream have applied the patch. It will be included in 2.10.26.

------- Comment #8 From Diego E. 'Flameeyes' Pettenò 2007-06-23 16:23:44 0000 ------- 
I've committed the patch to the tree to avoid cyclic dependencies between
mftrace and lilypond about fontforge.

------- Comment #9 From SpanKY 2007-06-28 09:44:56 0000 ------- 
thanks everyone
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug