From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] portage updates
Date: Thu, 23 Feb 2012 11:24:17 +0000 [thread overview]
Message-ID: <20120223112417.7a7e3e8f@hactar.digimed.co.uk> (raw)
In-Reply-To: <20120223131601.158ccfd7@khamul.example.com>
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
On Thu, 23 Feb 2012 13:16:01 +0200, Alan McKinnon 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).
It's not just you, although it doesn't appear to be that random.
Generally the portage update comes at or near the end of the list here.
At least you get the rest of the world update done before a broken new
portage renders it unusable :-/
--
Neil Bothwick
Normal people believe that if it ain't broke, don't fix it. Engineers
believe that if it ain't broke, it doesn't have enough features yet."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-02-23 11:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 11:16 [gentoo-user] portage updates Alan McKinnon
2012-02-23 11:24 ` Neil Bothwick [this message]
2012-02-23 11:48 ` Alan McKinnon
2012-02-23 14:07 ` Willie WY Wong
2012-02-23 15:13 ` Alan McKinnon
2012-02-24 1:36 ` Peter Humphrey
2012-02-24 5:56 ` Alan McKinnon
2012-02-24 7:03 ` Willie WY Wong
2012-02-24 9:04 ` Neil Bothwick
2012-02-24 10:27 ` Pandu Poluan
2012-02-24 15:36 ` Alan McKinnon
2012-02-27 21:05 ` Mike Gilbert
2012-02-28 0:37 ` Peter Humphrey
2012-02-28 11:23 ` Alex Schuster
2012-02-28 15:30 ` Peter Humphrey
2012-02-29 16:27 ` Alex Schuster
2012-02-29 20:09 ` Mick
2012-03-01 2:33 ` John
2012-03-01 3:24 ` Dale
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120223112417.7a7e3e8f@hactar.digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox