I've been using kdevelop-4.7.0 (unstable) for a while and it was working just fine. Then about a couple weeks ago it's ebuild got deleted from the portage tree and replaced with kdevelop-4.7.1 which is broken (I have issues with remote debugging).
Why does a good ebuild gets replaced with a broken one? Is there any way to make sure that packages that I'm using don't get removed from the portage tree or at least that the package doesn't get downgraded automatically. Right now if I install an unstable package by keywording a specific version and it gets deleted you get downgraded the next time you run emerge -vauDN so you have no simple way of going back to your working configuration since the ebuild is gone. -- Fernando Rodriguez
