You are only browsing one thread in the discussion! All comments are available on the post page.

Return

stevecrox ,
@stevecrox@mastodonapp.uk avatar

@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

MartinR OP ,

The proposal isn’t mine, I just read and shared it :-) The blog post has a paragraph or two about multpile subfolders, as I read it, the specification is not clear on whether thats supported? But actually: at first glance I think this would be better to have, because it would possibly make synchronizing to a new PC/Laptop even easier. However, this only works if any machine-specific settings (e.g. “offset /size of window”) are not stored in config, as that might break if you sync config between a multi-monitor setup and a single-monitor setup. This requires a lot of thought…

Molecular0079 ,

That feels way too nested to be useful IMHO. It’s great for packaging dev tools, but not really for handling config directories for user space apps. I just want ~/.config/KDE/<app>

happyhippo ,

I always considered plasma to be a part/sub project of kde, therefore org.kde.plasma would seem correct-er.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • random
  • [email protected]
  • All magazines
    •