| 1 |
I originally did that to see the difference between 'emerge system' and |
| 2 |
'emerge world', since system packages are supposed to only be the ones |
| 3 |
necessary for the operation of the system. |
| 4 |
|
| 5 |
I have a lot of boxes that I manage, so I can't always afford the |
| 6 |
compile time/downtime on all of them, so I mostly just 'emerge system' |
| 7 |
on those boxes. |
| 8 |
|
| 9 |
Then I look at the 'emerge world' output to see if I really need to |
| 10 |
update the boxes with those packages, since they are mostly version |
| 11 |
bumps and may not be as critical. |
| 12 |
|
| 13 |
|
| 14 |
Matt |
| 15 |
|
| 16 |
Ian P. Christian wrote: |
| 17 |
> On Thursday 15 September 2005 08:45, z3rosix@×××××××.ch wrote: |
| 18 |
> |
| 19 |
>>maybe i'm wrong but doens't "emerge -pv world" include "emerge -pv |
| 20 |
>>system" ??? |
| 21 |
>>so you just need to "emerge world" |
| 22 |
>>and bye the way you can use "emerge --sync -q" so you got only erros |
| 23 |
>>emailed. |
| 24 |
> |
| 25 |
> |
| 26 |
> I was curious as to why that was done too. Eitherway, doing an emerge world |
| 27 |
> will still leave out of date, possibly insecure packages on the system, so I |
| 28 |
> wouldn't advise relying on that. |
| 29 |
> |
| 30 |
-- |
| 31 |
gentoo-server@g.o mailing list |
Archives