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