On 12/20/2012 03:00 PM, Ian Stakenvicius wrote: > > > sorry for the format, this was > Sent from my iPhone > > On 2012-12-20, at 4:51 PM, Ciaran McCreesh <ciaran.mccre...@googlemail.com> > wrote: > >> On Thu, 20 Dec 2012 15:09:45 -0500 >> Rich Freeman <ri...@gentoo.org> wrote: >>> On Wed, Dec 19, 2012 at 4:43 AM, Zac Medico <zmed...@gentoo.org> >>> wrote: >>>> On 12/18/2012 11:58 PM, Duncan wrote: >>>>> I didn't know that. Last I knew, stable portage had special-case >>>>> acceptance of @system and @world to prepare the way, but I hadn't >>>>> seen that full /etc/portage/sets/* and /var/lib/portage/world_sets >>>>> support was stabilized. >>>>> >>>>> If indeed it is as you say, I've even more to rejoice about! =:^) >>>> >>>> Yeah, it's only been in stable for a few months now, so lots of >>>> people aren't aware of it yet. >>>> >>>> The current list available in portage-2.1.10.x, reported by emerge >>>> --list-sets is: >>>> >>>> preserved-rebuild >>> >>> If @preserved-rebuild and the corresponding FEATURES=preserve-libs are >>> now stable, we should create a news item about this. >>> >>> Otherwise people will still be running revdep-rebuild a decade from >>> now, as this feature was never formally announced as far as I'm aware, >>> and all the mentions of it were ages ago and not available to stable >>> users at the time. >> >> We really shouldn't... EAPI 5 is the way to go, not preserve-libs. >> > > preserved-libs complements EAPI5, it should not disappear.
Plus, if we are somehow able to do away with preserve-libs then we also need to ban preserve_old_lib from eutils.eclass, since it's the same thing only worse due to its lack of automatic garbage collection. -- Thanks, Zac
