When using emerge <file>, like for example emerge /lib/modules or emerge @module-rebuild portage will always try to upgrade the relevant packages even when a specific version or slot of these packages is defined in the world file. I'm not sure if this is deliberate or not but I expected this to honor what's in my world file. I ran into this because of the following: - I use a specific version of a module (nvidia in this case) and want to have control when I update it, so it's installed using a specific slot. - Now when updating my kernel and doing an emerge @module-rebuild portage tries to upgrade it to a newer version but then says it can't because of a slot conflict Reproducible: Always Steps to Reproduce: 1. Install/store in world an older stable version of a module 2. Run emerge @module-rebuild or emerge /lib/modules Actual Results: Slot conflict Expected Results: Rebuild of the relevant packages
