| 1 |
El jue, 20-12-2012 a las 12:23 -0800, Zac Medico escribió: |
| 2 |
> On 12/20/2012 12:09 PM, Rich Freeman wrote: |
| 3 |
> > On Wed, Dec 19, 2012 at 4:43 AM, Zac Medico <zmedico@g.o> wrote: |
| 4 |
> >> On 12/18/2012 11:58 PM, Duncan wrote: |
| 5 |
> >>> I didn't know that. Last I knew, stable portage had special-case |
| 6 |
> >>> acceptance of @system and @world to prepare the way, but I hadn't seen |
| 7 |
> >>> that full /etc/portage/sets/* and /var/lib/portage/world_sets support was |
| 8 |
> >>> stabilized. |
| 9 |
> >>> |
| 10 |
> >>> If indeed it is as you say, I've even more to rejoice about! =:^) |
| 11 |
> >> |
| 12 |
> >> Yeah, it's only been in stable for a few months now, so lots of people |
| 13 |
> >> aren't aware of it yet. |
| 14 |
> >> |
| 15 |
> >> The current list available in portage-2.1.10.x, reported by emerge |
| 16 |
> >> --list-sets is: |
| 17 |
> >> |
| 18 |
> >> preserved-rebuild |
| 19 |
> > |
| 20 |
> > If @preserved-rebuild and the corresponding FEATURES=preserve-libs are |
| 21 |
> > now stable, we should create a news item about this. |
| 22 |
> > |
| 23 |
> > Otherwise people will still be running revdep-rebuild a decade from |
| 24 |
> > now, as this feature was never formally announced as far as I'm aware, |
| 25 |
> > and all the mentions of it were ages ago and not available to stable |
| 26 |
> > users at the time. |
| 27 |
> |
| 28 |
> It's not enabled by default yet though. In the following blog post I've |
| 29 |
> mentioned that I would like to wait for EAPI 5 and automatic rebuilds |
| 30 |
> (via sub-slots and slot-operators) to gain widespread adoption before |
| 31 |
> preserve-libs is enabled by default: |
| 32 |
> |
| 33 |
> http://blogs.gentoo.org/zmedico/2012/09/21/preserve-libs-available-in-portage-2-1/ |
| 34 |
> |
| 35 |
> The reason that I want to wait is that EAPI 5 automatic rebuilds provide |
| 36 |
> solutions for known problems with @preserved-rebuild. These problems |
| 37 |
> include symbol collisions [1] and unnecessary rebuilding of packages |
| 38 |
> that are eligible for removal by emerge --depclean [2]. |
| 39 |
> |
| 40 |
> [1] |
| 41 |
> http://blog.flameeyes.eu/2008/06/a-few-risks-i-see-related-to-the-new-portage-2-2-preserve-libs-behaviour |
| 42 |
> [2] https://bugs.gentoo.org/show_bug.cgi?id=364425 |
| 43 |
|
| 44 |
Regarding symbol collisions, they would appear when people don't rebuild |
| 45 |
packages after updating (and that would be solved with eapi5, no? But, |
| 46 |
it's not exactly the same as is occurring currently if people forget to |
| 47 |
run revdep-rebuild (or if it's partially run)? |
Archives