On 02/20/2010 01:43 PM, Orcan Ogetbil wrote: > On Sat, Feb 20, 2010 at 6:26 AM, Luis Garrido wrote: > >>> I understand. But there is a strict Fedora policy here that a fonts >>> file must go to /usr/share/fonts (period) >>> (I can try dealing with this with symlinks though. Yet I still have to >>> patch the fonts out of the .qrc file) >>> This is mainly to avoid duplication of system fonts. If these feta and >>> parmesan fonts were available in Fedora, then I was going to remove >>> your copy of font files altogether and make the patch such that >>> rosegarden points to the system feta and parmesan fonts. >>> >>> >> Ah, but that rationale doesn't apply here at all. You see, sometimes a >> font is not exactly a font, and it is used in such way by the >> application that doesn't make any sense outside it. >> >> > This is exactly what I said when we were asked to separate the font > files. They didn't want to make an exception, which I had to accept. > Not that I am kind of tempted to leave the fonts in the binary because > their font file detection scripts will not find them anymore. :) This > was not the case with 1.7.3 where the fonts were installed separately > and we were getting yelled at. Should I cheat? :) > > Orcan > > > Those fonts are part of the lilypond package anyway, openSUSE lilypond puts them under /usr/share/lilypond/fonts, seeing that lilypond is needed for rosegarden anyway why can't the lilypond ones be used? Regards Dave P
------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
