Re: [gentoo-user] How can I update *every* ebuild?

[Dale]

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!