| 1 |
On Thursday 01 May 2008, reader@×××××××.com wrote: |
| 2 |
> Alan McKinnon <alan.mckinnon@×××××.com> writes: |
| 3 |
> > [2] vi /var/lib/portage/world |
| 4 |
> |
| 5 |
> What if I emerge -vC all I know I don't want. |
| 6 |
> |
| 7 |
> All kde all gnome all xorg for example, before update world. |
| 8 |
|
| 9 |
It seems fine in theory, but every time I've done it in real life I get |
| 10 |
into deep dependency trees that take more time to sort out than simply |
| 11 |
emerging world first. |
| 12 |
|
| 13 |
The trouble seems to be that it's easy to spot the high level packages |
| 14 |
that bring in all their DEPENDS - things like kde,gnome,xorg-x11. It's |
| 15 |
harder to spot the dependencies that want to bring everything back in |
| 16 |
again. kde is easy - the string 'kde' shows up in most of the names. |
| 17 |
gnome is harder as the names are much more randomly chosen. |
| 18 |
|
| 19 |
Plus, emerge --depclean will refuse to run until emerge world returns |
| 20 |
nothing to do. So you first have to get all the gui stuff out of the |
| 21 |
world file, identify *all* installed gui packages not in world and |
| 22 |
emerge -C them, then run emerge world followed by emerge --depclean. |
| 23 |
|
| 24 |
Like I said, I have found every time I've done it that it actually took |
| 25 |
longer and wasted more of my time and caused more frustration than just |
| 26 |
building kde. At least when building kde I could walk away and come |
| 27 |
back tomorrow. Fiddling world requires you to be there, watch the |
| 28 |
screen, decide, type next command, repeat. |
| 29 |
|
| 30 |
|
| 31 |
|
| 32 |
-- |
| 33 |
Alan McKinnon |
| 34 |
alan dot mckinnon at gmail dot com |
| 35 |
|
| 36 |
-- |
| 37 |
gentoo-user@l.g.o mailing list |
Archives