KDE

I answered something similar elsewhere:

If you mean migrating the files yourself, it's just a matter of copying the file from the old place ~/.config/yourconfigrc to ~/.config/yourapp/yourconfigrc.

If you mean you want the application to manage the migration itself, that's an implementation detail I hadn't thought about yet, but which I assume wouldn't be difficult to do with KConfig.

You can see this bit of code from Konsole showing how to migrate from old entries to new entries in the same config file for example: >https://invent.kde.org/utilities/konsole/-/blob/master/src/main.cpp#L99

The implementation could probably be something similar, with two KConfig/KSharedConfigPtr instances I assume 👀 so:

• if oldConfig exists, create an object for it
• read all oldConfig entries
• if it differs from newConfig, store which ones differ
• write all different oldConfig entries in newConfig object
• sync()

Something like that.

i agree with all of this, and in fact would go a step further to say: nicer names in general. what in the nine is plasma-org.kde.plasma.desktop-appletsrc‽ why not just plasma-appletsrc?

i think the real problem is the manpower to do it all though

@MartinR the Maven convention for packaging is a group identifer/package is the inverse domain order.

Taking plasma-org.kde.desktop-appletsrc you would create a group identifer of: org.plasma.kde.desktop With the artefact identifier being: appletsrc.

The folder structure would then look like:

.config  
\-\>org  
\-\>-\>plasma  
\-\>-\>-\>kde  
\-\>-\>-\>-\>desktop  
\-\>-\>-\>-\>-\>appletsrc  

Its simple