It would be immensely helpful if I could prevent portage from cleaning up certain paths. A practical example: I use ati-drivers on my machine, and I also help out the kernel developers with the latest kernels (currently have 2.6.27-rc5, 2.6.27-rc6, Linus' master branch, and Ingo's x86/tip branch). So basically, I need to be able to install ati-drivers with multiple kernels. I'd much rather not build/install ati-drivers outside of portage's control, because then I have unmanaged files that might not get pruned later on when they're outdated or whatnot. Unfortunately, if I emerge ati-drivers with 2.6.27-rc5 and then emerge with 2.6.27-rc6, the driver I installed for rc5 gets cleaned up in the process, leaving me with only 1 kernel with the driver installed. So it'd be useful to be able to blacklist certain paths. In this case, /lib/modules. Thoughts? Reproducible: Always Steps to Reproduce:
While the old package instance gets unmerged, the actual kernel modules should stay as /lib/modules is already blacklisted for file removals. Did the modules really get removed in your case, or did you just assume that they are no longer there?
I saw it "unmerge" the modules, but I just checked if they still exist, and they do. Bugger. I should have investigated further.
