https://bugs.kde.org/show_bug.cgi?id=422529

--- Comment #9 from Artem S. Tashkinov <a...@gmx.com> ---
(In reply to Volker Krause from comment #8)
> 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.

Lots of people do not want to see all their KDE configuration files under
`~/.config`.

XFCE for instance has its own prefix `~/.config/xfce4` which makes it easy to
reset XFCE settings without touching anything else.

KDE makes it wholly impossible and not only that, ~/.config with KDE5 installed
looks like a complete mess.

I'm pretty sure `~/.config` is hardcoded somewhere and changing it to e.g.
`~/.config/kde6` must be relatively easy. I've no idea what the right component
is, I'm not a KDE developer, I don't have to know that. I want that to be
fixed, and not only me, but other people as well.

I also don't quite understand the whole "migration" issue. I believe nothing
should be migrated automatically. People who upgrade from KDE5 to KDE6 will
have a brand new clean environment unless they manually move the necessary
files. It's actually a good thing. Less junk, fewer issues related to older
config files.

I also don't understand why you paint it as something complicated which could
have its pitfalls. KDE3 had it's own `~/.kde3` path which was changed to
`~/.config`. I don't remember any significant issues or arguments over that.
Someone just did it.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to