On Wednesday 30 April 2008, [EMAIL PROTECTED] wrote:
> Once I followed the recipe above all that disappeared along with the
> list error. I think that older version of portage was really what
> was causing most of the trouble.
Makes sense. Portage is rather fond of finding the kind of files and
directories it expects to find <grin> funny that <big grin>
> At this point I have profile set to 2008-server and have completed an
> eix-sync with that profile active. I've now also trimmed the use
> list in make.conf down removing any x related ones and only using a
> few I know I want and a few left from the prior list that looked
> harmless. Also added a few `-' ones to be sure. (I hate maildir for
> example.)
>
> grep USE /etc/make.conf:
>
> USE=" -arts -X -xorg -maildir
> mbox emacs logrotate readline samba smb usb zlib
>
> Some may be redundant there.. but I doubt any will get me in
> trouble.
Looks fine from here
> I've test run emerge -vuDNp world and see no blockages.
>
> I'd like to get rid of a bunch of X stuff but not really sure how
> best to go at it. I really don't want to set thru the grinding of
> kde and really don't want X at all on this vmware.
>
> Would it work to that end if I edit the world file removing x related
> apps before running emerge -vuDNp world and with the new use flags in
> place.
>
> Or will that leave herds of stuff on board?
There are two ways, I've tried them both. One is long, boring and
relatively easy [1] the other is potentially shorter, exciting, a test
of your skill and proves you have TheRightStuff [2] much as editing
main.cf by hand proves the same...
[1] emerge -avuND world, resolve blocks, run to completion.
emerge -av --depclean, make sure nothing desired will go away.
If so, emerge -n <package you want to keep>
Rinse, repeat
emerge -avuND world to check nothing more to be done
revdep-rebuild -p -i as a sanity check
[2] vi /var/lib/portage/world
Edit at will with sense of abandon
vi /etc/make.conf
Edit where appropriate
vi /etc/portage/*
Fearlessly edit throwing caution to the winds
loop_entry:
emerge -avuND world
Resolve blockers
emerge --resume --skipfirst (bonus points if you correctly
predict which packages will fail to build)
emerge -av --depclean
goto loop_entry
Having recently been through [2] I recommend you do [1] instead. In an
effort to avoid remerging all of gnome (which I wanted to remove
anyway, and takes about 8 hours to build) I caused myself to battle
with emerge --resume --skipfirst over the course of 4 days. Note that
the machine was mostly unusable for those 4 days. Go figure.
--
Alan McKinnon
alan dot mckinnon at gmail dot com
--
[email protected] mailing list
