On 12/20/2012 12:35 PM, Pacho Ramos wrote: > El jue, 20-12-2012 a las 12:23 -0800, Zac Medico escribió: >> On 12/20/2012 12:09 PM, Rich Freeman 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. >> >> It's not enabled by default yet though. In the following blog post I've >> mentioned that I would like to wait for EAPI 5 and automatic rebuilds >> (via sub-slots and slot-operators) to gain widespread adoption before >> preserve-libs is enabled by default: >> >> http://blogs.gentoo.org/zmedico/2012/09/21/preserve-libs-available-in-portage-2-1/ >> >> The reason that I want to wait is that EAPI 5 automatic rebuilds provide >> solutions for known problems with @preserved-rebuild. These problems >> include symbol collisions [1] and unnecessary rebuilding of packages >> that are eligible for removal by emerge --depclean [2]. >> >> [1] >> http://blog.flameeyes.eu/2008/06/a-few-risks-i-see-related-to-the-new-portage-2-2-preserve-libs-behaviour >> [2] https://bugs.gentoo.org/show_bug.cgi?id=364425 > > Regarding symbol collisions, they would appear when people don't rebuild > packages after updating (and that would be solved with eapi5, no? But, > it's not exactly the same as is occurring currently if people forget to > run revdep-rebuild (or if it's partially run)?
The problem with symbol collisions is only possible for people who have preserve-libs enabled. On the other hand, when preserve-libs is disabled, programs simply fail to run due to the libraries that they linked against having been unmerged when the library was updated. -- Thanks, Zac
