Duing my 'emerge world' I happened to be watching over the screen. I noticed 'pwlib' spitting out a warning telling me to unmerge first or else it will fail "You've been warned" it said. While I appreciate the warning, I let it go on anyway, thinking.. well, 'emerge world' shouldn't require user-intervnention during the process. So, it failed (on openh323 right after pwlib). I unmerged both packages, re-ran 'emerge world'.. went smoothly. WhatI propose here is that there is some kind of mechanism to inform 'emerge' that a specific port requires to be unmerged first prior to any upgrade. This way at least, we can avoid expecting the user to break out of the process, unmerge, then go back again. Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: I expect to be able to 'emerge world' and not touch the keyboard later until I have to do an etc-update ;)
Blockers should probably provide this functionality already... beyond that, sticking a notice in an ebuild to do something lest your system be completely fscked isn't great behaviour on the ebuild author's part...
