https://bugs.kde.org/show_bug.cgi?id=422529
Volker Krause <vkra...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vkra...@kde.org
--- Comment #8 from Volker Krause <vkra...@kde.org> ---
I don't think KConfig is the right place for this. The library one happens to
use for accessing a config file shouldn't just add its own vendor prefix. I can
see why we might want some grouping of the config files, but that should be per
product or product group (say Akonadi-based PIM or Plasma), not per config
library vendor.
Should someone want to implement this, this also needs considering migrating
existing files and we need to account for application code that for whatever
reason searches for config file locations manually. So this is much more than
just adding an extra prefix in one place. Whether that effort/risk is worth the
gain is another question.
--
You are receiving this mail because:
You are watching all bug changes.
