As seen below I had to manually interrupt the command even I specified a wrong (non-existant) package: unmerging should stop in such a case, or ? n22 ~ # emerge unmerge bluez-utils luez-libs --- Couldn't find luez-libs to unmerge. net-wireless/bluez-utils selected: 2.19 protected: none omitted: none >>> 'Selected' packages are slated for removal. >>> 'Protected' and 'omitted' packages will not be removed. >>> Waiting 5 seconds before starting... >>> (Control-C to abort)... >>> Unmerging in: 5 4 3 2 1 Exiting on signal 2
questionable IMO.
Transactional merges, yes, randomly die on errors, no ;)
In svn r3186 I've changed the behavior so that emerge will exit with error status when the user has attempted to unmerge a package that is not installed. My reasoning is that it's ambiguous to exit with success status when given erroneous input.
Released in 2.1_pre10.
Lots of people complained about this change, include the release engineering project. Sometimes we just have to go with the flow...so this is reverted in svn r3548.
See bug 134466 for a similar change that was reverted due to popular demand. :)
