On Thu, Feb 23, 2012 at 6:16 AM, Alan McKinnon <alan.mckin...@gmail.com> wrote: > > Historically, when an update to portage came available, portage would > put it at the head of the list, build it first, then re-run emerge > world command. > > I've seen lately that this no longer happens, portage updates are any > old place in the list just like all other packages. > > I'm wondering why this change happened, or if I somehow unknowingly set > an option to disable the old behaviour )I'd liek it back). >
Relevent commits: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=d3f704a425a50b5cfa997a25866929b30f1b7d0f http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=458ce208ed25f2d17666926585e14da6166eb9d7
