My question is about when you are maintaining a custom kernel, how do people normally deal with configuration every time they build it?
Is it considered ‘safe’ to copy the old .config over the new .config? Any gotchas to be aware of?
I feel like manually configuring the kernel every time you build it (with menuconfig for example) seems inefficient and someone would have figured out a better way.
When your build is done, check for the existence of .config.current. That is how your kernel is currently configured. Diff it against the original config if you want. If you’re happy with it, rename .config.current to whatever Manjaro now names the default config (it used to be config.x86_64).
Now the fun part…go and comment out all of the make menuconfig, etc lines in your PKGBUILD. Next time you build a kernel, you shouldn’t have to have any interaction from the time you invoke makepkg until you’re finished.
If you need to make subsequent config changes, re-enable (remove the # from a config line) and you’re all set.