From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-user+bounces-144694-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id 470C4138644
for <garchives@archives.gentoo.org>; Thu, 24 Jan 2013 07:22:27 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 3B64821C031;
Thu, 24 Jan 2013 07:22:16 +0000 (UTC)
Received: from mail-ee0-f47.google.com (mail-ee0-f47.google.com [74.125.83.47])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id 7A88421C001
for <gentoo-user@lists.gentoo.org>; Thu, 24 Jan 2013 07:22:14 +0000 (UTC)
Received: by mail-ee0-f47.google.com with SMTP id e52so4378896eek.34
for <gentoo-user@lists.gentoo.org>; Wed, 23 Jan 2013 23:22:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=x-received:date:from:to:subject:message-id:in-reply-to:references
:organization:x-mailer:mime-version:content-type
:content-transfer-encoding;
bh=qZq5Az3vsF3bvZP6pYflARGCXUs7viIfGxVHiAHx1sI=;
b=OAdgNWp91x2KQY4ijPZ9HGNvxCKD8v9E/Gbxr/BXp+2t4uMCo/PsnRCTwHdJvcrhPL
2SAyTWH8wmkpgfcqy8h3xlfq3B/zJylZ0QwUXwvvBSOR3GZxuCDjowlPsRy4JZowNSGq
71+eZNtNJPV3r8DQp7XQkXmEpmTi/PTgGXUk1WgJ0hbOjWwiowzqG2ACtbYmdv5hZn8K
FhTcYFkrLghVXv9nfw8avkew0NvBA2Bo4KzstKOBR3XDQZ1Uu+dYxmb1puKQ9At3GkmG
OKEjYVr2Gto5A52rxixD9Syg63rmCxJgkZ9qDWJpsAWKDRem96eOCK0UkDyPOM1KH/DD
7VKQ==
X-Received: by 10.14.194.199 with SMTP id m47mr3657457een.11.1359012132912;
Wed, 23 Jan 2013 23:22:12 -0800 (PST)
Received: from khamul.example.com (196-210-183-218.dynamic.isadsl.co.za. [196.210.183.218])
by mx.google.com with ESMTPS id q5sm19130923eeo.17.2013.01.23.23.22.10
(version=SSLv3 cipher=RC4-SHA bits=128/128);
Wed, 23 Jan 2013 23:22:11 -0800 (PST)
Date: Thu, 24 Jan 2013 09:21:38 +0200
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How can I update *every* ebuild?
Message-ID: <20130124092138.293f757e@khamul.example.com>
In-Reply-To: <51003E73.2080201@gmail.com>
References: <51003E73.2080201@gmail.com>
Organization: Internet Solutions
X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.14; x86_64-pc-linux-gnu)
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Archives-Salt: 709c2448-2ccd-4c9d-a834-7f794869b446
X-Archives-Hash: 0c33444904878d16851e735196f552ef
On Wed, 23 Jan 2013 20:48:03 +0100
Jarry <mr.jarry@gmail.com> wrote:
> Hi Gentoo-users,
> I always thought the right way to update everything was:
>
> emerge --update --deep --newuse world
> emerge --update --deep --newuse system
>
> When I try the above mentioned, nothing to update is found.
> Yet when I try i.e. "emerge --pretend nasm", I see:
>
> [ebuild U ] dev-lang/nasm-2.10.05 [2.10.01]
>
> So there is apparently update for dev-lang/nasm, yet it was
> not pulled when I tried to update the "world" or "system".
> And who knows for how many other ebuilds there is update
> available...
>
> So how can I update really *every* ebuild?
What are your bdep settings in make.conf? (see man emerge for more info
on bdeps)
nasm is unlikely to be a run-time depend for anything, considering
what it does it's more likely to be a build depend. If nothing in world
that uses nasm to build itslef is to be built, then nasm won't be
upgraded; it will be left as-is until it really does need to be
rebuilt.
You should learn to trust portage, it knows more about your system than
you do. "really update every package" sounds a lot more like pedantic
OCD insistence that it all be done always rather than a sensible
decision :-) And before anyone rips me a new one for being
unbelievably rude to list users again, I have the same issue myself. So
I got really good at spotting it and recognizing why it is not really a
good thing.
--
Alan McKinnon
alan.mckinnon@gmail.com