In "Kernel Upgrade Guide" there is no section concerning what additional actions should be done on kernel upgrade (apart from configuring/compiling/installing a new kernel version). There are definitely several packages that should be remerged, as well as gensplash's initrd created, additional kernel modules rebuilt (like nvidia, wi-fi, and so on), etc. Reproducible: Couldn't Reproduce Steps to Reproduce: - Actual Results: Currently there is no documentation (or at least I couldn't easily find it) on this matter. "Gentoo Linux Kernel Upgrade Guide" is the closest shot, but it doesn't mention any of the additional actions the user should do while upgrading the kernel. Expected Results: I would recommend to add a section in "Gentoo Linux Kernel Upgrade Guide", where such actions (additional actions the user should do while upgrading the kernel) could be described. Probably some ebuilds could be enhanced too, to warn user what packages should be upgraded. I know, dependencies should handle most of the situations, but I remember that once after upgrading the kernel as well as gnome-vfs with changed API for udev/dbus/hal, the latter (hald to be specific) stopped working. It quietly refused to start, so there was no process as "hald" in memory. All that was needed was to remerge hald package (as its ebuild checks for the kernel version and compiles some things using this knowledge) and everything went back to normal.
http://www.gentoo.org/doc/en/kernel-upgrade.xml#doc_chap6 I'm inclined to mark this bug INVALID unless you've got better reasons :)
Yes, I know that my request might look a bit selfish, but it's hard to keep track of ALL the packages that have been installed, that have to be recompiled in the event of kernel upgrade. If I emerge myself a package that depends on the kernel, I may write down this fact somewhere and then use it as a check-list when upgrading the kernel. But if a package is pulled in as a dependency of another one that I wanted? (true - it's hypothetical, but possible) How could I guess that it needs to be recompiled? On the other hand, a similar notification "recompile this-and-that on kernel upgrade" could be put into ebuilds themselves. But stating that, I suppose noone would like to implement such a feature anytime soon :( Go ahead, you can mark the bug INVALID, but this is a small sign that one day something will have to be done in this matter. Maybe asking for a documentation is a bit too much, but maybe this should be done in software (read: portage, eclasses, ebuilds, etc) instead. Thanks anyway for taking care.
I think most of such rebuilds are triggered by using sys-kernel/module-rebuild.
Wow. That's brilliant! I've tried this today... It's quite fresh (ver. 0.1 May, ver. 0.5 August). But, wow. Thanks, thanks, thanks! The portage tree is indeed full of surprises :-) Maybe then I should ask for mentioning sys-kernel/module-rebuild in the "Kernel Upgrade Guide"? It would be just one paragraph. And if it's considered stable, why not recommend such a nice tool to the users? And at the same time to decrease the number of module-related bug reports??
I've added a paragraph about module-rebuild.
