I keep getting nagged by Portage to update umpteen or so config files in my /etc. Gee I wonder what is it. Turns out it's /etc/genkernel.conf yet again. Config updates are an important way to communicate breaking changes in configs. This is not meant to communicate the fact that maintainers chose to: 1. Use some words in comments in uppercase 2. Use different amount of "=" signs in a comment, in a section that has a lot of them in a row, like 10-20 3. Convert entire comment to uppercase With changes like this, I am less likely to treat Portage's nagging with the seriousness it deserves. Reproducible: Always Steps to Reproduce: 1. Install genkernel and have your own config 2. Wait a few months and update genkernel again Actual Results: Most of the config changes suggested by dispatch-conf are related to words used in comments. This is pointless. Expected Results: I should only be looking at suggested changes to /etc/genkernel.conf when there are new parameters available, not when devs fix typos and re-arrange comments.
Created attachment 870894 [details, diff] Example of null changes proposed by Portage
You can configure dispatch-conf to auto-merge comments: /etc/dispatch-conf.conf: # Automerge files comprising only whitespace and/or comments # (yes or no) replace-wscomments=no
You're basically asking for AI to detect when config updated may be relevant for you. It's not going to happen.
