1 |
On Wednesday 30 April 2008, reader@×××××××.com wrote: |
2 |
|
3 |
> Once I followed the recipe above all that disappeared along with the |
4 |
> list error. I think that older version of portage was really what |
5 |
> was causing most of the trouble. |
6 |
|
7 |
Makes sense. Portage is rather fond of finding the kind of files and |
8 |
directories it expects to find <grin> funny that <big grin> |
9 |
|
10 |
> At this point I have profile set to 2008-server and have completed an |
11 |
> eix-sync with that profile active. I've now also trimmed the use |
12 |
> list in make.conf down removing any x related ones and only using a |
13 |
> few I know I want and a few left from the prior list that looked |
14 |
> harmless. Also added a few `-' ones to be sure. (I hate maildir for |
15 |
> example.) |
16 |
> |
17 |
> grep USE /etc/make.conf: |
18 |
> |
19 |
> USE=" -arts -X -xorg -maildir |
20 |
> mbox emacs logrotate readline samba smb usb zlib |
21 |
> |
22 |
> Some may be redundant there.. but I doubt any will get me in |
23 |
> trouble. |
24 |
|
25 |
Looks fine from here |
26 |
|
27 |
> I've test run emerge -vuDNp world and see no blockages. |
28 |
> |
29 |
> I'd like to get rid of a bunch of X stuff but not really sure how |
30 |
> best to go at it. I really don't want to set thru the grinding of |
31 |
> kde and really don't want X at all on this vmware. |
32 |
> |
33 |
> Would it work to that end if I edit the world file removing x related |
34 |
> apps before running emerge -vuDNp world and with the new use flags in |
35 |
> place. |
36 |
> |
37 |
> Or will that leave herds of stuff on board? |
38 |
|
39 |
There are two ways, I've tried them both. One is long, boring and |
40 |
relatively easy [1] the other is potentially shorter, exciting, a test |
41 |
of your skill and proves you have TheRightStuff [2] much as editing |
42 |
main.cf by hand proves the same... |
43 |
|
44 |
[1] emerge -avuND world, resolve blocks, run to completion. |
45 |
emerge -av --depclean, make sure nothing desired will go away. |
46 |
If so, emerge -n <package you want to keep> |
47 |
Rinse, repeat |
48 |
emerge -avuND world to check nothing more to be done |
49 |
revdep-rebuild -p -i as a sanity check |
50 |
|
51 |
[2] vi /var/lib/portage/world |
52 |
Edit at will with sense of abandon |
53 |
vi /etc/make.conf |
54 |
Edit where appropriate |
55 |
vi /etc/portage/* |
56 |
Fearlessly edit throwing caution to the winds |
57 |
loop_entry: |
58 |
emerge -avuND world |
59 |
Resolve blockers |
60 |
emerge --resume --skipfirst (bonus points if you correctly |
61 |
predict which packages will fail to build) |
62 |
emerge -av --depclean |
63 |
goto loop_entry |
64 |
|
65 |
|
66 |
Having recently been through [2] I recommend you do [1] instead. In an |
67 |
effort to avoid remerging all of gnome (which I wanted to remove |
68 |
anyway, and takes about 8 hours to build) I caused myself to battle |
69 |
with emerge --resume --skipfirst over the course of 4 days. Note that |
70 |
the machine was mostly unusable for those 4 days. Go figure. |
71 |
|
72 |
|
73 |
|
74 |
-- |
75 |
Alan McKinnon |
76 |
alan dot mckinnon at gmail dot com |
77 |
|
78 |
-- |
79 |
gentoo-user@l.g.o mailing list |