Bugzilla Bug 74561

I was cleaning up my use-flags with ufed, and I found that there's a "local
flag" freetype for x11-wm/metisse ... but a quick grep freetype inside the
/usr/portage/profiles/use.* files give me that:

/usr/portage/profiles/use.desc:truetype - Adds support for FreeType and/or
FreeType2 fonts
/usr/portage/profiles/use.local.desc:app-office/pointless:freetype - Enables
Freetype font support
/usr/portage/profiles/use.local.desc:media-libs/gd:freetype-version-1 - if for
some reason you want to use freetype v1 instead of v2
/usr/portage/profiles/use.local.desc:media-video/transcode:freetype - Enables
Freetype font support
/usr/portage/profiles/use.local.desc:x11-base/kdrive:freetype - Enables
Freetype font support
/usr/portage/profiles/use.local.desc:x11-libs/fox:freetype - Enable freetype
support (allows for antialiased fonts)
/usr/portage/profiles/use.local.desc:x11-wm/metisse:freetype - Enable freetype
font support

So we have 5 ebuilds with "local" flag freetype to enable freetype support, and
a global truetype flag.
I think this should be changed having only the truetype flag. If this is the
case, I can submit the patches for all the ebuilds involved, should I?

HTH,
Diego

I found other problems on transcode ebuild so I posted a bug cleaning it a
little bit. I think this so this bug can depend on that at least.

yes, filing bugs for all those packs should be fine, mark them as blockers vs
this one (like you already did).

Ok now all the packages using the freetype flag should be fixed by the blocking
bugs :)

Still missing kdrive and metisse cleanup, we have only those two now.

Considering that pointless doesn't need it anymore...