Summary: | sys-kernel/module-rebuild doesn't understand "build-on-demand" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Chris Slycord <cslycord> |
Component: | Current packages | Assignee: | Gentoo Kernel Miscellaneous <kernel-misc> |
Status: | RESOLVED OBSOLETE | ||
Severity: | trivial | CC: | bug.hunter |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 410739 | ||
Bug Blocks: |
Description
Chris Slycord
2006-04-15 23:44:36 UTC
I know of a way that I could fix this, but I was reluctant to do so since it might break a few other ebuilds out there. That said, it would make sense to me to do so. its possible for me to check MODULE_NAMES in postinst (in the linux-mod eclass) and not add it to the db if its a null string, but I wont have chance to look at this until at the very earliest next week. this problem is related to a problem i do have with vmware. each time a new kernel is installed i have manually run vmware-config.pl to rebuild the kernel modules of vmware. wouldn't it be a better solution to extend or change module-rebuild in a way that solves this problem too? i don't know how module-rebuild exactly works. therefore i try to sketch how i think it should/could work to solve the above problem. there should be a way for each ebuild to not just add the ebuild to the ebuilds that have to be rebuild but instead to register an arbitrary command to rebuild the kernel-modules. ebuilds that are only kernel-modules (like nvidia-kernel) would just add an emerge command, while other, like vmware, would add "ebuild /var/pkg/.../<pkg>.ebuild config" or even other commands. this would allow arbitrary ways to rebuild the kernel modules. of course there are ways for module-rebuild to optimize the commands, e.g. to merge all emerge-commands into one command. sorry, i forgot to mention how my idea is relatet to this thread. my way how module-rebuild could work would allow for a none command for the fuse-ebuild, when there is no need to rebuild anything. ups, forgot another needed change to module-rebuild. module-rebuild must allow the execution of commands that need interaction with the user, like the -ask option of emerge or the questions the user has to answer for "vmware-config.pl". FYI, this is "fixed" in portage-2.2, where the current existence of module-rebuild is replaced with: emerge @module-rebuild This will not re-emerge fuse, assuming that the most recently installed fuse did not install kernel modules. (kernel modules may be left over from previous merges, portage never removes them) Leaving this bug open until portage-2.2 is stable and we have released a transitionary module-rebuild package # Samuli Suominen <ssuominen@gentoo.org> (28 Dec 2013) # Replaced by 'emerge @module-rebuild' set in Portage itself. # Removal in 30 days, see http://bugs.gentoo.org/410739 sys-kernel/module-rebuild |