| 1 |
On Tue, 2009-01-13 at 10:25 -0600, Paul Hartman wrote: |
| 2 |
> On Tue, Jan 13, 2009 at 10:02 AM, Mike Kazantsev |
| 3 |
> <mike_kazantsev@×××××××.net> wrote: |
| 4 |
> > On Tue, 13 Jan 2009 17:52:05 +0200 |
| 5 |
> > Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 6 |
> > |
| 7 |
> >> read the man page. |
| 8 |
> >> |
| 9 |
> >> Especially the bit about bdeps - these are usually not included |
| 10 |
> >> in 'emerge -uND world' but will be included when you use -e |
| 11 |
> > |
| 12 |
> > I'd also suggest checking out the @installed set. |
| 13 |
> |
| 14 |
> Thanks, I haven't tried that before... emerge -up @installed gives me |
| 15 |
> quite a surprising result: |
| 16 |
> |
| 17 |
> Total: 290 packages (9 upgrades, 2 downgrades, 122 new, 157 in new |
| 18 |
> slots), Size of downloads: 190,301 kB |
| 19 |
> Conflict: 3 blocks (3 unsatisfied) |
| 20 |
> |
| 21 |
> It seems to want to install all of KDE4 (which I'm not using... not |
| 22 |
> sure why that is?), aside from that, though, there are a handful of |
| 23 |
> non-KDE packages that do show up for upgrades/downgrades. |
| 24 |
|
| 25 |
My guess is that you are using KDE3? If that's the case then what |
| 26 |
'emerge -up @installed' *is likely* doing is: |
| 27 |
|
| 28 |
for each package in @installed: |
| 29 |
emerge -u package |
| 30 |
|
| 31 |
So, e.g. if you have kopete-3 installed then it will want to upgrade to |
| 32 |
kopeted-4. It's doing what you tell it to, though not exactly what you |
| 33 |
expected. The "handful of non-KDE packages" is are likely dependencies |
| 34 |
(whether build-time or run-time) of said packages. |
| 35 |
|
| 36 |
I myself don't see any reason to use "-u @installed". For example on my |
| 37 |
system it wants to upgrade musicbrainz to 3.0.2, but musicbrainz is not |
| 38 |
in my world file and I don't have anything that depends on 3.0.2 (only |
| 39 |
2.1.*) so it's an unnecessary upgrade. My guess is that a subsequent |
| 40 |
--depclean will unmerge it anyway. |
| 41 |
|
| 42 |
-a |
Archives