| 1 |
On Tue, 2009-01-13 at 09:44 -0600, Paul Hartman wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> I normally do "emerge -uDvN @world" (or in other words "emerge |
| 5 |
> --update --deep --verbose --newuse @world"). Right now, it tells me |
| 6 |
> this: |
| 7 |
> |
| 8 |
> Total: 0 packages, Size of downloads: 0 kB |
| 9 |
> |
| 10 |
> I also --depclean on a regular basis to remove any unneeded packages. |
| 11 |
> Right now, it tells me this: |
| 12 |
> |
| 13 |
> No packages selected for removal by depclean |
| 14 |
> |
| 15 |
> Based on those two commands, I'm led to believe I have a fully updated |
| 16 |
> system. So, then, I am curious why when I do "emerge -e @world" it |
| 17 |
> tells me this: |
| 18 |
> |
| 19 |
> Total: 1432 packages (9 upgrades, 2 downgrades, 14 new, 1407 |
| 20 |
> reinstalls, 1 interactive), Size of downloads: 76,235 kB |
| 21 |
> |
| 22 |
> How is that possible? Where do those upgrades, downgrades and new |
| 23 |
> packages come from? What is missing from my traditional "-uDvN" |
| 24 |
> command that is causing me to miss some of those updates? |
| 25 |
|
| 26 |
Well for one "emerge -e" will pull in build-time dependencies which |
| 27 |
"emerge -u" won't (unless it's necessary for an upgrade). So |
| 28 |
hypothetically let's say you have firefox in your world file, and you |
| 29 |
have the latest so "emerge -u @world" doesn't pick it up, but say you |
| 30 |
"emerge -e @world" and firefox needs "=automake-1.6.*" to build, but you |
| 31 |
don't have that version anymore because, say --depclean or something |
| 32 |
else cleared it out or you have automake-1.6.1 installed but it's no |
| 33 |
longer in portage but 1.6.3 is, then automake-1.6.3 might show up as New |
| 34 |
or Upgrade or even Downgrade (since it's slotted). |
| 35 |
|
| 36 |
-a |
Archives