I want a clean config directory!

This is a companion discussion topic for the original entry at http://localhost:1313/kconfig/

This is a companion discussion topic for the original entry at http://localhost:1313/kconfig/

I’d like to read this, but I’m pretty sure there’s no blog running on port 1313 on my computer :upside_down_face:


I rather just have a clean home directory, but we can’t expect these things. :rofl:

1 Like


Is the question related to purging redundant configuration parameters and/or attributes and/or meta-data and/or database records?

Hi! To find out what I can do, say @konqi display help.

Where shall I type the following text?

@konqi display help

I currently know how to do the following things:

@konqi start {name-of-tutorial}

Starts an interactive tutorial just for you, in a personal message. {name-of-tutorial} can be one of: tutorial, advanced tutorial.

@konqi roll 2d6

:game_die: 3, 6

@konqi quote

:left_speech_bubble: I hear and I forget. I see and I remember. I do and I understand. — Confucius

@konqi fortune

:crystal_ball: You may rely on it

@konqi start tutorial

A personal message appeared:

Thanks for joining KDE Discuss, and welcome!

If you’d like to learn more, select below and bookmark this personal message. If you do, there may be a :gift: in your future!

@Herzenschein it looks like the URLs in your RSS feed are minced: Planet KDE on rabbiticTranslator and they’re all pointing to localhost :slight_smile:

Mine points to localhost as well.

I followed @Duha’s link and it is a very good read.

1 Like


If I’m understanding you correctly, you’re proposing to use C++ language properties to keep the KDE Plasma configuration settings clean of historical no longer used attributes.

  • At least from the point of view of the team responsible for the code.

The question is, how will someone responsible for a given configuration file, check for unused Crud in the configuration file instances on everyone else’s machines?


I am not the author of the blog post! I just shared the link to the blog post because the drkonqi link is broken.


Thanks for the heads up – maybe the author of Konqi Blog post can correct the mistake –

  • Other Konqi Blog posts seem to be just fine …

I wonder if KConfig has the functionality to automatically migrate config files (or maybe, fall back to reading the old location?)

Yeah, major oopsie.

I reinstalled my main VPS and started using podman for everything and did a lot of changes recently, it might have borked something.

I also didn’t notice that hugo server always assumes a localhost environment, so if you use it as a service in production it simply starts pointing to localhost for things, especially in other languages…

1 Like

Probably worth deleting this discuss post? It was already posted before here :smiley:

I knew I read this before! I was just unsure if it was on discuss or planet.

I think its fine if it stays up since a few people in this post mentioned that they didn’t see it before, but liked the post (so there are probably more :slight_smile: .

If you still want to remove it, its probably better to hide it instead of deleting it (since then it gets removed instead of showing a empty post.)

1 Like

AFAIK removing the cruft is not needed. You just need to have a new config file and have the app point to that, preferring that over the old one.

The real issue is migration, but that shouldn’t be that complicated either. I can think of something like this:

  • create an object for newConfig
  • read all newConfig entries
  • 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
  • write to disk with sync()

KConfig is easy enough that you can easily bundle that in a single function.