| 1 |
On 04/16/2013 11:50 AM, Tanstaafl wrote: |
| 2 |
> On 2013-04-16 11:28 AM, Michael Mol <mikemol@×××××.com> wrote: |
| 3 |
>> To be clear, you didn't rebuild the entire system. You rebuilt core |
| 4 |
>> packages. To rebuild the entire system, it'd be: |
| 5 |
>> |
| 6 |
>> emerge -e @world |
| 7 |
> |
| 8 |
> Correct - which is why I said @system... ;) |
| 9 |
> |
| 10 |
>> # Plus whatever else there is. |
| 11 |
> |
| 12 |
> Hmmm... are there really packages that belong to neither @system or |
| 13 |
> @world? How would I go about finding/updating these? |
| 14 |
|
| 15 |
I must have missed where you ran emerge -e @world. Oops. :) |
| 16 |
|
| 17 |
But, yes, there are packages which don't belong to @system or @world. |
| 18 |
@world consists of things you've explicitly asked for. @system consists |
| 19 |
of things that are deemed inherently necessary for system operation. |
| 20 |
|
| 21 |
Neither necessarily contains things like x11-libs/libX11, which may be |
| 22 |
pulled in as a dependency of something in @world or @system (depending |
| 23 |
on USE flags, etc). Various python modules would also not be found in |
| 24 |
either @world or @system. @system and @world are explicit |
| 25 |
statements...there are still the dependencies to worry about. |
| 26 |
|
| 27 |
But if you ran emerge -e @world, the -e would have picked those up. |
| 28 |
|
| 29 |
[snip] |
Archives