Martin Vaeth wrote: > The user has to put a corrected ebuild into his overlay and must > reemerge the package (currently, the latter could be skipped with > dynamic deps). > In fact, no matter whether you have static or dynamic deps, this is > the only way to cleanly avoid the problems if you want to keep a > package installed which is not maintained anymore: > *You* must maintain it. There simply is no magic which can avoid this.
It could be avoided if portage tree sync applied each tree change locally rather than jump from old to new. There was a delta idea discussed a year or so ago in connection with some git discussions. The user's vardb could then automatically receive the last state of the ebuild, before it was removed. That's no small change though. //Peter
