On 02/16/2011 09:54 AM, Khaled Hosny wrote: > On Tue, Feb 15, 2011 at 10:44:07PM -0200, Rogério Brito wrote: >> http://packages.qa.debian.org/f/fontforge/news/20110118T151726Z.html > > And you can only build lilypond fonts with long double enabled fontforge > (those need to be built since they are Matafont fonts), so we just > introduce a bug to fix a non-bug. Sounds like fontforge needs to be modified to use long-doubles (or not) as a runtime option instead of a compile-time option? Or we introduce two fontforge binary packages, one built with long doubles and one without? (that seems like an ugly solution to me) or maybe there are some other ways to solve this problem for both packages (and for future packages)? --dkg
Attachment:
signature.asc
Description: OpenPGP digital signature