The information in the ebuilds of >=media-libs/freetype-2.4 about the TrueType bytecode interpreter no longer being patented (and any remaining patent issues regarding subpixel rendering) should be reflected in the 'use.local.desc' descriptions of the 'auto-hinter' and 'bindist' USE flags. Reproducible: Always Steps to Reproduce: equery u freetype (with >=app-portage/gentoolkit-0.3) Actual Results: * Found these USE flags for media-libs/freetype-2.4.4: U I + + X : Adds support for X11 - - auto-hinter : Use the unpatented auto-hinter instead of the (recommended) TrueType bytecode interpreter - - bindist : Flag to enable or disable options for prebuilt (GRP) packages (eg. due to licensing issues) - - debug : Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see http://www.gentoo.org/proj/en/qa/backtraces.xml - - doc : Adds extra documentation (API, Javadoc, etc) - - fontforge : Install internal headers required for TrueType debugger in media-gfx/fontforge (built with USE=truetype-debugger) - - utils : Install utilities and examples from ft2demos Expected Results: Description of 'auto-hinter' should not imply that the TrueType bytecode interpreter is still patented. Description of 'bindist' should explain what enabling the flag actually does for this package (apparently it's still needed because of ClearType patents?), instead of relying on the completely useless default description from 'use.desc'.
Fixed.
