On Mon, Jul 28, 2014 at 12:29 PM, Ian Stakenvicius <a...@gentoo.org> wrote: > As has been mentioned or alluded to before, this is fine as long as > end-users --sync when the dependency change is still in the tree. > However, if that doesn't happen then we still end up with the issue. > > Of course, if that is the case, then #2 shouldn't happen either > (because the end-user system wouldn't see B as having been removed and > therefore --depclean won't remove it).
Agree. Things stay consistent either way if everything is done properly. Bottom line is that if you keep PVs installed which aren't in portage, you're on your own. They could contain known bugs that we fixed in a revbump that you missed, or they could contain security issues that we don't bother to check for since we don't have the PV in our repository, etc. If you keep such a PV installed then you're the maintainer, so good luck! If a more recent version is in portage, then your old ebuild will probably uninstall cleanly (or at least as cleanly as it would with static deps), and the upgrade will hopefully be in better shape. Rich
