On K, 2015-01-07 at 07:29 +0100, Peter Stuge wrote: > $ grep :harfbuzz profiles/use*desc > profiles/use.local.desc:dev-libs/efl:harfbuzz - Enable complex text shaping > and layout support. > profiles/use.local.desc:dev-qt/qtgui:harfbuzz - Use media-libs/harfbuzz for > text shaping (experimental in Qt 5.3.x, default in Qt 5.4.0 and later). If > enabled, it can still be disabled at runtime by setting QT_HARFBUZZ > environment variable to "old". > profiles/use.local.desc:media-libs/freetype:harfbuzz - Use > media-libs/harfbuzz for auto-hinting OpenType fonts. WARNING: may trigger > circular dependencies! > profiles/use.local.desc:media-libs/libass:harfbuzz - Enables OpenType shaping > via media-libs/harfbuzz. > > Or isn't 4 enough?
I don't know about that, but I would say at least half of them should continue to carry on a specific description of what the USE flag does in its metadata.xml. I guess consider this just a friendly slightly unrelated reminder that when making USE flags global, please don't end up losing information by deleting the specific description. And consider adding a local description to a packages global USE flag usage if you can describe its effect more specifically. And if some tooling doesn't support that, well, bad luck. My tool does (less metadata.xml) Mart
