Archives
Archives
| From: | Mike Gilbert <floppym@g.o> | ||
|---|---|---|---|
| To: | gentoo-user@l.g.o | ||
| Subject: | Re: [gentoo-user] portage updates | ||
| Date: | Mon, 27 Feb 2012 21:07:19 | ||
| Message-Id: | CAJ0EP43gF9dA8neTLRxqHaEa2+CQzcfBODxFN-_--Ta02Zi3tA@mail.gmail.com | ||
| In Reply to: | [gentoo-user] portage updates by Alan McKinnon |
||
| 1 | On Thu, Feb 23, 2012 at 6:16 AM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 2 | > |
| 3 | > Historically, when an update to portage came available, portage would |
| 4 | > put it at the head of the list, build it first, then re-run emerge |
| 5 | > world command. |
| 6 | > |
| 7 | > I've seen lately that this no longer happens, portage updates are any |
| 8 | > old place in the list just like all other packages. |
| 9 | > |
| 10 | > I'm wondering why this change happened, or if I somehow unknowingly set |
| 11 | > an option to disable the old behaviour )I'd liek it back). |
| 12 | > |
| 13 | |
| 14 | Relevent commits: |
| 15 | |
| 16 | http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=d3f704a425a50b5cfa997a25866929b30f1b7d0f |
| 17 | http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=458ce208ed25f2d17666926585e14da6166eb9d7 |
| Subject | Author |
|---|---|
| Re: [gentoo-user] portage updates | Peter Humphrey <peter@××××××××××××××.org> |