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

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

[Jarry]

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?

Jarry

-- 
_______________________________________________________________
This mailbox accepts e-mails only from selected mailing-lists!
Everything else is considered to be spam and therefore deleted.

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

[Florian Philipp]

[-- Attachment #1: Type: text/plain, Size: 848 bytes --]

Am 23.01.2013 20:48, schrieb Jarry:
> 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?
> 
> Jarry
> 

That's because nasm is only a build-dependency. Portage will update it
when it is required for building the next time. Use "--with-bdeps y" to
change that.

Regards,
Florian Philipp



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

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

[Michael Mol]

On Wed, Jan 23, 2013 at 2:48 PM, 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?

Well, terminology issue first.

An 'ebuild' is a file describing how the system handles a specific
version of a particular package. So what you probably want to do is
update every *package*.

And in answer...you've got it right. (Though I would use @world and/or
@system, rather than leaving off the @)

Why nasm isn't getting updated might have something to do with your
packages.mask file.

--
:wq

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

[Hilco Wijbenga]

On 23 January 2013 11:53, Michael Mol <mikemol@gmail.com> wrote:
> On Wed, Jan 23, 2013 at 2:48 PM, Jarry <mr.jarry@gmail.com> wrote:
<snip/>
>> emerge --update --deep --newuse world
>> emerge --update --deep --newuse system
<snip/>
>> So how can I update really *every* ebuild?
>
> And in answer...you've got it right. (Though I would use @world and/or
> @system, rather than leaving off the @)

Why? While "@world" refers to the world set explicitly, it does
exactly the same as "world", doesn't it?. You could save a whole
character! ;-) More seriously, the @ character isn't easy to type so
I'd rather avoid it unless there is a real benefit to using it.

More to the point, doing "emerge ... system" *after* "emerge ...
world" seems pointless. World includes system so I would expect
everything in system to already have been updated. It would make more
sense to start with "emerge ... system" but even then: what is the
advantage over simply (only) running "emerge ... world"?

Cheers,
Hilco

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

[Michael Mol]

On Wed, Jan 23, 2013 at 3:07 PM, Hilco Wijbenga
<hilco.wijbenga@gmail.com> wrote:
> On 23 January 2013 11:53, Michael Mol <mikemol@gmail.com> wrote:
>> On Wed, Jan 23, 2013 at 2:48 PM, Jarry <mr.jarry@gmail.com> wrote:
> <snip/>
>>> emerge --update --deep --newuse world
>>> emerge --update --deep --newuse system
> <snip/>
>>> So how can I update really *every* ebuild?
>>
>> And in answer...you've got it right. (Though I would use @world and/or
>> @system, rather than leaving off the @)
>
> Why? While "@world" refers to the world set explicitly, it does
> exactly the same as "world", doesn't it?. You could save a whole
> character! ;-) More seriously, the @ character isn't easy to type so
> I'd rather avoid it unless there is a real benefit to using it.

I don't know about your keyboard layout, but in en-us, @ is shift-2,
which is pretty easy. And if you type cross-host email addresses at
all (since the 80s, anyway), @ should come naturally. :)

So, to answer 'why':

1. Newer versions of portage have broader support for sets. Using @
when talking about sets is useful for maintaining your understanding
that you're working with sets.
2. While it may well never happen (unless portage drops support for
resolving 'world' to mean '@world'), if there is ever a package named
'world', then "emerge world" when asking for the @world set will be
ambiguous, and lead to surprising results.

If you use apostrophes and punctuation in normal writing, a single @
in an infrequently-typed command shouldn't pose much of a problem. :)

>
> More to the point, doing "emerge ... system" *after* "emerge ...
> world" seems pointless. World includes system so I would expect
> everything in system to already have been updated. It would make more
> sense to start with "emerge ... system" but even then: what is the
> advantage over simply (only) running "emerge ... world"?

That, I don't know. I usually just emerge -uDN @world, followed by
emerge --depclean, followed by revdep-rebuild. And if I'm writing a
script[1], I'll throw --resume in there somewhere. And maybe cycle it
until everything comes out clean

[1] https://github.com/mikemol/gentoo-install

--
:wq

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

[Bruce Hill]

On Wed, Jan 23, 2013 at 08:48:03PM +0100, Jarry 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?

This alias is in /root/.bashrc:

alias ud='eix-sync && emerge -aDjNuv @world && dispatch-conf && emerge -a --depclean && revdep-rebuild -i && clear && exit'

emerge -aDjNuv @world

a = ask (Yes/No prompt -- don't waste time with --pretend)
D = deep (consider the entire dependency tree of packages)
j = jobs (no number after j means to run as many simultaneously as possible)
N = newuse (pkgs with changed USE flags)
u = update (to the best version available)
v = verbose
@world = world set

"man emerge" would be very enlightening for you...

It's important to sync (eix-sync) before you start, or your local portage tree
won't have any new software; and equally important to check configs
(dispatch-conf), clean out pkgs no longer needed (--depclean), and rebuild any
deps (revdep-rebuild). Don' forget to read news (eselect news read).

Running this ud alias every morning with coffee on no less than 8 Gentoo boxen
on this LAN keeps everything updated, clean, and I'm usually one of the first
to find new bugs. Well, since my test machine running ~amd64 is no longer in
service, there are less bugs. But, still, there are enough bugs in amd64.

Cheers,
Bruce
-- 
Happy Penguin Computers               >')
126 Fenco Drive                       ( \
Tupelo, MS 38801                       ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting

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

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 259 bytes --]

On Wed, 23 Jan 2013 15:21:35 -0600, Bruce Hill wrote:

> N = newuse (pkgs with changed USE flags)

--changed-use makes more sense than -N, it saves unnecessary compiling.


-- 
Neil Bothwick

Mac screen message: "Like, dude, something went wrong."

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

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

[Bruce Hill]

On Wed, Jan 23, 2013 at 10:27:54PM +0000, Neil Bothwick wrote:
> On Wed, 23 Jan 2013 15:21:35 -0600, Bruce Hill wrote:
> 
> > N = newuse (pkgs with changed USE flags)
> 
> --changed-use makes more sense than -N, it saves unnecessary compiling.

If I understand "man emerge", --newuse tells me if an installed package has a
USE flag that was added, removed, turned on, or turned off; whereas
--changed-use only notifies me if a USE flag that I've chosen on my installed
packages are changed -- not any other USE flags the maintainer, or some other
committer, has changed (those have bitten me in the past).

Since I'm not really interested in reading the ChangeLog for *hundreds* of
packages, N (--newuse) suits me better. Those flags have special colors and
one or more of - * % () symbols so a quick glance lets me know *which* pkgs
the dev has changed, and *which* pkgs ChangeLog I might want to read.
-- 
Happy Penguin Computers               >')
126 Fenco Drive                       ( \
Tupelo, MS 38801                       ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting

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

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]

On Wed, 23 Jan 2013 17:01:11 -0600, Bruce Hill wrote:

> > > N = newuse (pkgs with changed USE flags)  
> > 
> > --changed-use makes more sense than -N, it saves unnecessary
> > compiling.  
> 
> If I understand "man emerge", --newuse tells me if an installed
> package has a USE flag that was added, removed, turned on, or turned
> off; whereas --changed-use only notifies me if a USE flag that I've
> chosen on my installed packages are changed -- not any other USE flags
> the maintainer, or some other committer, has changed (those have bitten
> me in the past).

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.


-- 
Neil Bothwick

This is the day for firm decisions! Or is it?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

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

[Bruce Hill]

On Wed, Jan 23, 2013 at 11:15:10PM +0000, Neil Bothwick 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.
-- 
Happy Penguin Computers               >')
126 Fenco Drive                       ( \
Tupelo, MS 38801                       ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting

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

[Dale]

Michael Mol wrote:
> On Wed, Jan 23, 2013 at 3:07 PM, Hilco Wijbenga
> <hilco.wijbenga@gmail.com> wrote:
>> On 23 January 2013 11:53, Michael Mol <mikemol@gmail.com> wrote:
>>> On Wed, Jan 23, 2013 at 2:48 PM, Jarry <mr.jarry@gmail.com> wrote:
>> <snip/>
>>>> emerge --update --deep --newuse world
>>>> emerge --update --deep --newuse system
>> <snip/>
>>>> So how can I update really *every* ebuild?
>>> And in answer...you've got it right. (Though I would use @world and/or
>>> @system, rather than leaving off the @)
>> Why? While "@world" refers to the world set explicitly, it does
>> exactly the same as "world", doesn't it?. You could save a whole
>> character! ;-) More seriously, the @ character isn't easy to type so
>> I'd rather avoid it unless there is a real benefit to using it.
> I don't know about your keyboard layout, but in en-us, @ is shift-2,
> which is pretty easy. And if you type cross-host email addresses at
> all (since the 80s, anyway), @ should come naturally. :)
>
> So, to answer 'why':
>
> 1. Newer versions of portage have broader support for sets. Using @
> when talking about sets is useful for maintaining your understanding
> that you're working with sets.
> 2. While it may well never happen (unless portage drops support for
> resolving 'world' to mean '@world'), if there is ever a package named
> 'world', then "emerge world" when asking for the @world set will be
> ambiguous, and lead to surprising results.
>
> If you use apostrophes and punctuation in normal writing, a single @
> in an infrequently-typed command shouldn't pose much of a problem. :)
>
>> More to the point, doing "emerge ... system" *after* "emerge ...
>> world" seems pointless. World includes system so I would expect
>> everything in system to already have been updated. It would make more
>> sense to start with "emerge ... system" but even then: what is the
>> advantage over simply (only) running "emerge ... world"?
> That, I don't know. I usually just emerge -uDN @world, followed by
> emerge --depclean, followed by revdep-rebuild. And if I'm writing a
> script[1], I'll throw --resume in there somewhere. And maybe cycle it
> until everything comes out clean
>
> [1] https://github.com/mikemol/gentoo-install
>
> --
> :wq
>
>

All I ever do is emerge -uvaDN world and it catches everything.  If you
use plain world, it includes the system set.  If you use @world, then
some things in the @system set may not be upgraded. 

Dale

:-)  :-) 

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

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

[Alan McKinnon]

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

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

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]

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.


-- 
Neil Bothwick

Friends may come and go, but enemies accumulate.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

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

[Dale]

[-- Attachment #1: Type: text/plain, Size: 2465 bytes --]

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!



[-- Attachment #2: Type: text/html, Size: 3374 bytes --]

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

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1930 bytes --]

On Thu, 24 Jan 2013 03:17:06 -0600, Dale wrote:

> 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 that, but it is not relevant to my point. Using -N includes
packages that do not need emerging. Either you let them emerge or you
filter them out manually, either way is inefficient. Particularly the
manual filtering as they will show up again on the next run.

Bruce also posted a chained alias he uses, so having to interrupt the
process top manually select packages means running the rest of the
commands manually too. Like Alan says, trust portage to know your system,
let it make the first decision before you review it with --ask.

The option is there, I find it useful. I really don't care who else uses
itWhat 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.
, but I thought I'd mention it in came anyone still using its shotgun
predecessor found the information useful. I am not trying to persuade
anyone else to use it and you won't persuade me to stop using it, neither
is the point of the post.

It's just occurred to me as I was about to hit Send. If you respond to
emerge --ask with n, it still returns success, so using that in the
middle of a chin of commands is not much help unless you use Ctrl-C
instead of n.


-- 
Neil Bothwick

I doubt therefore I might be.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

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

[Dale]

[-- Attachment #1: Type: text/plain, Size: 2712 bytes --]

Neil Bothwick wrote:
> On Thu, 24 Jan 2013 03:17:06 -0600, Dale wrote:
>
>> 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 that, but it is not relevant to my point. Using -N includes
> packages that do not need emerging. Either you let them emerge or you
> filter them out manually, either way is inefficient. Particularly the
> manual filtering as they will show up again on the next run.
>
> Bruce also posted a chained alias he uses, so having to interrupt the
> process top manually select packages means running the rest of the
> commands manually too. Like Alan says, trust portage to know your system,
> let it make the first decision before you review it with --ask.
>
> The option is there, I find it useful. I really don't care who else uses
> itWhat 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.
> , but I thought I'd mention it in came anyone still using its shotgun
> predecessor found the information useful. I am not trying to persuade
> anyone else to use it and you won't persuade me to stop using it, neither
> is the point of the post.
>
> It's just occurred to me as I was about to hit Send. If you respond to
> emerge --ask with n, it still returns success, so using that in the
> middle of a chin of commands is not much help unless you use Ctrl-C
> instead of n.
>
>

Why do you say that -N will compile packages that don't need it?  If a
USE flags is added, changed or whatever, I want that change to be seen
and the package to be recompiled.  It could very well affect how the
package works or some feature.

I can see the point on the long command tho.  About the longest I get is
eix-sync && emerge -uvaDN world.  That's about it.  I like to type in
anything else that needs to be dealt with.  As you know, I run into
enough problems with upgrades already.  LOL 

Oh, eudev switch went pretty well.  I even found a roach in dracut.  It
seems dracut had a hard dependency on udev itself and not the virtual
udev.  Now dracut is gone.

Dale

:-)  :-)

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


[-- Attachment #2: Type: text/html, Size: 3766 bytes --]

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

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 818 bytes --]

On Thu, 24 Jan 2013 03:46:09 -0600, Dale wrote:

> Why do you say that -N will compile packages that don't need it?  If a
> USE flags is added, changed or whatever, I want that change to be seen
> and the package to be recompiled.  It could very well affect how the
> package works or some feature.

If you built a package with USE="-foo" and the foo USE flag is later
removed, -N would rebuild it, --changed-use would not.

Now think about all those linguas variables that are expanded to USE
flags. Do you really want to recompile LibreOffice just because a
linguas_klingon USE flag has been added? One that you wouldn't use anyway
and so makes no difference to the software you actually have installed.


-- 
Neil Bothwick

A computer without Microsoft is like a chocolate cake without mustard.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

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

[Kerin Millar]

On 24/01/2013 09:46, Dale wrote:
> Neil Bothwick wrote:
>> On Thu, 24 Jan 2013 03:17:06  -0600, Dale wrote:

<snip>

> Why do you say that -N will compile packages that don't need it?  If a
> USE flags is added, changed or whatever, I want that change to be seen
> and the package to be recompiled.  It could very well affect how the
> package works or some feature.

There are various situations in which it can indeed be a waste of time. 
For example, running emerge -auDN @world prompts me to rebuild gcc:

[ebuild   R    ] sys-devel/gcc-4.6.3  USE="(-go%)"

Why? Because the toolchain eclass was recently modified to better 
support the Go programming language. But wait! I didn't have the "go" 
flag enabled before because it didn't exist. Nor will it be enabled in 
the prospective rebuild. What's more, I couldn't enable it even if I 
wanted to because it's masked for this version of gcc (as indicated by 
the parentheses).

The upshot is that rebuilding gcc now would serve absolutely no purpose. 
The --changed-use parameter understands this whereas -N does not.

Cheers,

--Kerin

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

[Jean-Christophe Bach]

[-- Attachment #1: Type: text/plain, Size: 232 bytes --]

<SNIP>

> Do you really want to recompile LibreOffice just because a
> linguas_klingon USE flag has been added?

Well… I think that linguas_klingon would exactly the use flag which would make
recompile LibreOffice ^^

JC

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

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

[Kerin Millar]

On 23/01/2013 19:48, Jarry 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?

Using --with-bdeps helps to some extent. If you really want to upgrade 
everything then this should work, assuming that portage-utils is installed:

emerge -au1 $(qlist -ICS)

In practice, one doesn't need to for the reasons stated elsewhere in 
this thread. Taking nasm as an example, if you use it and care about 
receiving timely updates then it ought to be in your world file, as it 
would be if installed explicitly.

Cheers,

--Kerin

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

[Yohan Pereira]

On 24/01/13 at 12:37pm, Neil Bothwick wrote:
> If you built a package with USE="-foo" and the foo USE flag is later
> removed, -N would rebuild it, --changed-use would not.
> 
> Now think about all those linguas variables that are expanded to USE
> flags. Do you really want to recompile LibreOffice just because a
> linguas_klingon USE flag has been added? One that you wouldn't use anyway
> and so makes no difference to the software you actually have installed.

Ok --changed-use seems awesome, I'm sold. Just one minor clarification. In
the above example, what if linguas_klingon was added and defaults
to being on, would --changed-use rebuild libreoffice? In this case
rebuilding would be the desirable thing to do I presume.

-- 

- Yohan Pereira

The difference between a Miracle and a Fact is exactly the difference
between a mermaid and a seal.
                -- Mark Twain

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

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 528 bytes --]

On Thu, 24 Jan 2013 19:08:13 +0530, Yohan Pereira wrote:

> Ok --changed-use seems awesome, I'm sold. Just one minor clarification.
> In the above example, what if linguas_klingon was added and defaults
> to being on, would --changed-use rebuild libreoffice? In this case
> rebuilding would be the desirable thing to do I presume.

Yes, but I think even the Gentoo devs would hesitate to make Klingon a
default language...


-- 
Neil Bothwick

Windows Error #05: Nonexisent error. This cannot really be happening

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

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

[Trevor D. Manning]

[-- Attachment #1: Type: text/plain, Size: 500 bytes --]

* Neil Bothwick (neil@digimed.co.uk) wrote:

<SNIP>
> , but I thought I'd mention it in came anyone still using its shotgun
> predecessor found the information useful. I am not trying to persuade
> anyone else to use it and you won't persuade me to stop using it, neither
> is the point of the post.

I found your advice quite useful, as I have done in the past.
Thanks for the information good sir... 

-- 
Trevor D. Manning

BOFH Excuse #227:

Fatal error right in front of screen

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

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

[Stroller]

On 23 January 2013, at 19:48, Jarry 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, ...
> 
> So how can I update really *every* ebuild?

Others have explained why this has happened.

I think `eix -Iuc` will show all packages on the system for which a version other than the latest is installed.

You can use `eix -Iu --only-names > file.txt` then you can edit the list before running `for foo in $(cat file.txt) ; do emerge -1 $foo ; done`. 

This is somewhat inelegant and others here will probably argue that there is no value to updating these packages.

If you have multiple slots of a package installed on your system (sources, Python, gcc) then they will appear on the list, even if you have the latest version of each slot installed. That's why you probably want to edit the list before performing the update.

Stroller.

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

[»Q«]

On Wed, 23 Jan 2013 17:37:19 -0600
Bruce Hill <daddy@happypenguincomputers.com> wrote:

> On Wed, Jan 23, 2013 at 11:15:10PM +0000, Neil Bothwick 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.

A new capability merits a revision bump if it's significant enough that
people need to see the change.  I'm content to let the devs make that
call, but that may be because I am not too bright.