On Fri, 27 Feb 2015 03:07:34 -0500 Fernando Rodriguez <frodriguez.develo...@outlook.com> wrote:
> > 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. > You can look in the packages Changelog in the portage tree, perhaps there's an entry there explaining why the old version was removed. ebuilds are never truly lost, if you still have it installed the ebuild is stored in /var/db. If not, you can find it in the gentoo attic (google can help), download it and put it in your local overlay. Mask the versions you don't want and portage will ensure your local copy stays installed. Alan
