The install process will install the nvidia kernel module in:<br> "/lib/modules/${KV}/kernel/video"<br> But if for some reason the user does a change to the kernel configuration and does a make modules_install the all /lib/modules/${KV}/kernel is deleted. So the next time the user tries to startx he will get an error and will have to redo a emerge nvidia-kernel .<br> This can be solved doing the install in for example:<br> "/lib/modules/${KV}/video".<br> The module will still be avilable and will not deleted when making a make modules_install.
this is something that the portage developers are working on and a known issue. What has so far come of the idea of kernel version slotting?
This is actually not related to slotting -- reread the post, we just need to move the module out of the "kernel" directory.
Daniel, does portage support multiple packages of the EXACT same version but with different SLOTs? AFAIK it does not, and that is what this problem would require as a solution, either that or support for maybe using the config-protect (or similar) methodology for the kernel modules directories to prevent the modules for previos kernels from being deleted upon compiling and installing modules for a newer version.
Created attachment 3005 [details] New ebuild with path fixed This e-build comes with a fixed path.
Brandon, you're right, we don't support different slots for identical versions of packages but we will eventually; it requires an update to our /var/db/pkg database format. Closing this bug as the -r1 rev of the ebuild fixes the problem.
