In testing out media-lib/svgalib 1.9.21 i noticed that the svgalib_helper module from 1.9.19 kept getting loaded and not the new 1.9.21. Although i did an emerge -C svgalib to remove my old 1.9.19 version, the module didn't get cleaned up. 1.9.19 ebuild sticks the kernel module under /lib/modules/<ver>/kernel/misc/svgalib_helper.ko and 1.9.21 ebuild sticks the module under /lib/modules/<ver>/misc/svgalib_helper.ko Reproducible: Always Steps to Reproduce: 1.emerge old svga lib 2.unmerge leaves old kernel module 3.emerge new version, both kernel modules are installed Actual Results: Old kernel module is getting loaded, not new one Expected Results: the new kernel module should get loaded
the behavior you're seeing is correct imo ... modules should not appear in the kernel/ subdir ... beyond adding a warning to the 1.9.21 ebuild, i dont see what else is to be done here ...
Agreed, the new behaviour is correct, the old bevahiour is not, and theres not really anything we can do about the "stale" module file being left over. Sorry for any inconvenience.