From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 2ED1A13864B for ; Thu, 24 Jan 2013 09:17:21 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E95CF21C049; Thu, 24 Jan 2013 09:17:11 +0000 (UTC) Received: from mail-gh0-f170.google.com (mail-gh0-f170.google.com [209.85.160.170]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4909F21C001 for ; Thu, 24 Jan 2013 09:17:10 +0000 (UTC) Received: by mail-gh0-f170.google.com with SMTP id g14so535202ghb.29 for ; Thu, 24 Jan 2013 01:17:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:x-enigmail-version:content-type; bh=p0BOELDki/EPmhiwrVVisCCLNppoV99TsOGdRl1tb+c=; b=Lm73s8nv9NQbaZETN5VUTtqipkeD75rNxV5F0LzHXyrvZBbOwJ0KS7jHWZCW30xE7B EQkMTM8Cd+P4VATWc6u1JjcZUVzA7VXABvgaXC+XmVMHVcyFPP0DdV17KX2FDS3BhW9i 9sTdh7IZIKnBXjljslKlCRzlf3arE+X/9sl9VCzaEXEyirXZELbgrfIAiuYIl3nCLBTr iTxIaKcIG1upnrsFG7XwOfeK9oj9GFHEes26tOFApM4fELrKs8NkCeB2uX2l0DAXsHmO yiFQPbrzJhagts277q+wn5evpMdYEEQiTYik/An90zs02f5zDBJzo3EpsrXSpt/0BCOQ 3m6A== X-Received: by 10.236.138.109 with SMTP id z73mr1183398yhi.72.1359019029289; Thu, 24 Jan 2013 01:17:09 -0800 (PST) Received: from [192.168.2.5] (adsl-74-240-57-140.jan.bellsouth.net. [74.240.57.140]) by mx.google.com with ESMTPS id w18sm2314648anl.14.2013.01.24.01.17.07 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Jan 2013 01:17:08 -0800 (PST) Message-ID: <5100FC12.5080808@gmail.com> Date: Thu, 24 Jan 2013 03:17:06 -0600 From: Dale User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15.1 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] How can I update *every* ebuild? References: <51003E73.2080201@gmail.com> <20130123212135.GO30998@server> <20130123222754.44b4bc13@digimed.co.uk> <20130123230111.GP30998@server> <20130123231510.107a6f55@digimed.co.uk> <20130123233719.GQ30998@server> <20130124083216.4b393db0@digimed.co.uk> In-Reply-To: <20130124083216.4b393db0@digimed.co.uk> X-Enigmail-Version: 1.5 Content-Type: multipart/alternative; boundary="------------040007020903000704090603" X-Archives-Salt: fde96cb5-2c5e-4e51-a27d-c91b4138d54d X-Archives-Hash: fbe3f0b41d0905250a80869e75d239ef This is a multi-part message in MIME format. --------------040007020903000704090603 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Neil Bothwick wrote: > On Wed, 23 Jan 2013 17:37:19 -0600, Bruce Hill wrote: > >>> That's right. So --changed-use only reemerges the package if the >>> change only affects your system, whereas -N will rebuild it even if >>> the changed flag is of no interest to you, such as when a flag you >>> were not using is removed. It saves recompiling packages for no >>> reason, which is presumably the reason it was added, it is a newer >>> option than -N. >> The purpose of -a (ask) is so you can see the stuff before taking >> action, and if it needs rebuilding then do it. Nothing is rebuilt just >> because it shows up in the output; but not seeing changes to a package >> you use that were made is not too bright. >> >> If you ever built from source before, I'm sure you didn't blindly build >> the software without reading ./configure --help and checking your >> options. > This has nothing to do with --ask, which I use almost all of the time. It > is about having portage make more sensible choices. You are free to use > whichever options you want, at no time did I tell you what to user, I > merely pointed out a potentially useful and time saving alternative. > > What Bruce was saying is this. When you use --ask, you can look at the output of what packages are going to be emerged, what USE flags are enabled/disabled/changed and other information that could make a person change a setting all before anything is done. If emerge is doing to much, to little or some other unwanted thing, you can change it. I understand what he is saying because this is what I do. Actually, I helped Bruce with some of his first installs over private email. I always do a emerge -uvaDN world because it catches most anything that needs to be updated. I have in the past omitted some of those to only have to go back and do it all over again but a little deeper. I also have this set in make.conf: EMERGE_DEFAULT_OPTS="--with-bdeps y --backtrack=30" among other preferences. I have found that over time, while I may have to emerge more packages, I run into less compatibility issues between package versions. I suspect that those options would likely be something the OP would want to consider. It does lead to more compile times on some updates but it seems to prevent some issues as well. I know for me, going deep seems to save time. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! --------------040007020903000704090603 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Neil Bothwick wrote:
> On Wed, 23 Jan 2013 17:37:19 -0600, Bruce Hill wrote:
>
>>> That's right. So --changed-use only reemerges the package if the
>>> change only affects your system, whereas -N will rebuild it even if
>>> the changed flag is of no interest to you, such as when a flag you
>>> were not using is removed. It saves recompiling packages for no
>>> reason, which is presumably the reason it was added, it is a newer
>>> option than -N.
>> The purpose of -a (ask) is so you can see the stuff before taking
>> action, and if it needs rebuilding then do it. Nothing is rebuilt just
>> because it shows up in the output; but not seeing changes to a package
>> you use that were made is not too bright.
>>
>> If you ever built from source before, I'm sure you didn't blindly build
>> the software without reading ./configure --help and checking your
>> options.
> This has nothing to do with --ask, which I use almost all of the time. It
> is about having portage make more sensible choices. You are free to use
> whichever options you want, at no time did I tell you what to user, I
> merely pointed out a potentially useful and time saving alternative.
>
>


What Bruce was saying is this.  When you use --ask, you can look at the output of what packages are going to be emerged, what USE flags are enabled/disabled/changed and other information that could make a person change a setting all before anything is done.  If emerge is doing to much, to little or some other unwanted thing, you can change it.

I understand what he is saying because this is what I do.  Actually, I helped Bruce with some of his first installs over private email.  I always do a emerge -uvaDN world because it catches most anything that needs to be updated.  I have in the past omitted some of those to only have to go back and do it all over again but a little deeper.  I also have this set in make.conf:  EMERGE_DEFAULT_OPTS="--with-bdeps y --backtrack=30" among other preferences.  I have found that over time, while I may have to emerge more packages, I run into less compatibility issues between package versions.

I suspect that those options would likely be something the OP would want to consider.  It does lead to more compile times on some updates but it seems to prevent some issues as well.  I know for me, going deep seems to save time.

Dale

:-)  :-)

--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!


--------------040007020903000704090603--