Portage drops the canoe, crushing my Gentoo installation

In the process of migrating to KDE as my desktop environment (selected as I have no experience with the newest versions, and I want an entire desktop environment as opposed to just a window manager) I decided to use the fateful eselect profile utility.

Gentoo has a system profile selector, where you can choose the Portage profile that best suits your environment and needs for the computer. My existing profile was default/linux/amd64/2008.0, and I decided to switch to default/linux/amd64/10.0/desktop. I then ran emerge –update –deep –newuse world to completely rebuild and update packages accordingly.

Bad idea.

Portage indicated that I had hundreds of dependency conflicts and refused to update or install additional packages, no doubt aggravated by my use of “autounmask” and Portato’s dependency resolver. The most visible problem was Ekiga depending on GTK+ 2.6, which depends on GNOME 2.26, which itself depends on Ekiga. It was a giant circular mess that left me unable to resolve dependencies. I tried all the traditional fixes, including depclean and trying to reset my package.keywords file.

Faced with an intermittently working desktop, I flattened and reinstalled the system last night and am continuing to get things back up in working order, this time with the QT libraries enabled. (KDE is currently compiling – I’m using twm, the default X window manager, to run a web browser.) A few things I noticed this time around:

  • Don’t necessarily put a whole ton of USE flags in your /etc/make.conf file at first. Portage is pretty good at telling you if a flag is required for a package, and you can always recompile something if you need to.
  • In the latest amd64/10.0/desktop profile, X.org comes with version 1.6. I had no end of difficulty getting an xorg.conf file created with X -configure – it would start and load with only a black screen. I ended up running X.org using startx, then using nvidia-config to generate a base file.
  • evdev (for input device support) works great, provided you have hal and dbus USE flags and the appropriate daemons are started. I didn’t even have to touch the input device section of xorg.conf.
  • Select your system profile first, before changing it will cause grief!



2 Trackbacks / Pingbacks

  1. Portage drops the canoe, crushing my Gentoo installation | The … | Just linux!
  2. Once again, portage perplexes and enrages me | The Linux Experiment

Leave a Reply

Your email address will not be published.


*