Re: Problem Emerging Gnome3 on Fresh Install

On Thu, Oct 17, 2013, at 10:44 AM, Tyrin Price wrote:
> Greetings,
> 
> I am a newbie to Gentoo but not new to Linux and I am having
> difficulty setting up Gnome3 on a fresh Gentoo install.
> 
> I've read many wiki entries and tips online. So far the best advice I
> received was on IRC but I am still stopped.
> 
> Here is what I have done:
> 
> Fresh install (amd64 architecture).
> 
> Added ACCEPT_KEYWORDS="~amd64" to /etc/portage/make.conf
> 
> Emerged dbus and added it to services started at boot time.
> 
> Changed profile to gnome/systemd
> 
> Now, I cannot figure out how to get around the problems shown when I
> try to emerge gnome.
> 
> http://pastebin.com/NsbycC27 shows the output of emerge gnome

[blocks B      ] sys-fs/udev ("sys-fs/udev" is blocking
sys-apps/systemd-208-r2)
[blocks B      ] <sys-apps/openrc-0.12 ("<sys-apps/openrc-0.12" is
blocking sys-apps/kmod-15)
[blocks B      ] sys-apps/systemd ("sys-apps/systemd" is blocking
sys-fs/udev-204)

Blocks 1 and 3 are the same: You can't have systemd and sys-fs/udev
installed simultaneously.  Block 2 is telling you you need to upgrade or
uninstall openrc before you pull in kmod-15.

However, I strongly suggest you *not* do a huge upgrade this way.  If
it's a new install and you are initally on "amd64" My recommendation is
to follow these steps:

1. Say on amd64.  Bring yourself to a consistent state (emerge -DuvaN
@world; revdep-rebuild; emerge --depclean --ask)
2. Switch to ~amd64.  Bring yourself to a consistent state. 
3. Switch to systemd (Read the wiki article). Bring yourself to a
consistent state.
4. emerge gnome.

Doing everything at once (IMO) is just a recipe for headaches.  The best
thing is to do smaller steps, verify, then move to the next step.  Sure
you can do everything in one step, but when there is a problem it will
be more difficult to figure out which change created which problem (was
it switching to testing? switching to systemd? etc.).

HTH,
-a