eselect kernel needs an option to automatically copy ".config" from the old src-dir to the new one, when the symlink is changed.
Bad idea to blindly reuse old .configs, IMHO... especially between different kernel patchsets.
(In reply to comment #1) > Bad idea to blindly reuse old .configs, IMHO... I agree, but it could be followed by a message about running make oldconfig. (i.e., so it is not done blindly anymore).
sorry for not writing so, but of course there should be a message about using "make oldconfig". just missed to write it, because it was so obvious for me.
That was not entirely what I suggested - make oldconfig just tends to produce crap for me if the kernels are too many versions apart or too different.
i never had that problem but i tend to upgrade my kernel regularly. nonetheless there should be an option to autocopy ".config". it will still be an _option_ and the message can be there.
Interesting idea. Go into a bit more depth of how you think it should work exactly please.
Bernd: Ping? Please provided with more details on how you want this feature to work. I.e, when switching from version A to B, and B has a '.config' file already, what should be done? This is you feature request after all.
sorry for not answering earlier. i never got the info-mail. my ideas are: 1. two additional options: --no-config-update and --config-update either can be default. 2. if no option is given, some default behavior combined with a question. e.g.: do you additionaly want to update your config? if option is given, do as wished without further questions. 3. copy .config file from old kernel-dir to new dir and either call "make oldconfig" or inform the user that he must call "make oldconfig" manually. 4. probably some check of kernel-versions. if the versions differe to much (e.g.: different major version ;) ) utter a big warning, that the user should carefully check what happens during "make oldconfig" or that "make oldconfig" may fail.
i would like to have the option as well.
Still interested in this feature? Then reopen this bug and attach a patch please.
(In reply to comment #10) > Still interested in this feature? Then reopen this bug and attach a patch > please. Seems not. WONTFIX then.