As pointed out from bug #74561 x11-base/kdrive ebuild is using a local freetype flag, instead of the truetype global one. Fixing this, I cleaned up use-flags for kdrive to more suit the ones of x11-base/xorg-x11 (so truetype-fonts take place of old truetype, truetype take place of freetype, and type1-fonts take place of type1). I also added dependency on freetype if truetype use-flag is used. HTH, Diego
Created attachment 46287 [details] kdrive-4.3.0-r5.ebuild
With small changes like this, can you attach a diff instead of a full ebuild?
Created attachment 46325 [details, diff] Patch over current ebuild Here it is :)
Looks good to me...
+ use truetype-fonts && echo "#define BuildXTrueType YES" >> config/cf/host.def \ That line is inappropriate. truetype-fonts is _only_ for building the fonts.
Then there's the problem to define a way to split truetype global useflag from what is achieved by truetype-fonts useflag as I used in my patch. Using truetype useflag like before, it's misused, because it's described as freetype dependency, but there the freetype dependency was freetype useflag. Maybe we can simply make truetype support always-in?
Just do 'em both with truetype. Now that I look at the patch again, type1-fonts is also inappropriate for the same reason.
Created attachment 46326 [details, diff] Updated patch removing truetype-fonts Ok, done :) I restored type1 instead of type1-fonts and removed truetype-fonts, now truetype useflag both add truetype fonts and freetype library.
*** Bug 75760 has been marked as a duplicate of this bug. ***
Finally applying this, after being prompted by swegener's recent post on bad USE flags on gentoo-dev.