<p>On Jul 27, 2013 4:44 PM, "walt" <<a href="mailto:w41ter@gmail.com">w41ter@gmail.com</a>> wrote:<br> ><br> > First hint: it's a mess -- don't do it on a critical machine.<br> > (My main machine is ~amd64 and that's why I'm doing it on virtual<br> > ~amd64 machines first.)<br> ><br> > The new gnome-shell demands that systemd be installed, even if you<br> > don't intend to use it.<br> ><br> > The latest systemd conflicts with udev because the udev project<br> > has been rolled into systemd, which now provides all of the files<br> > previously installed by udev.<br> ><br> > Therefore your machine will still boot without udev because systemd<br> > installs all the udev files. You don't need to start or use systemd<br> > if you don't want to, but the systemd package must be installed<br> > *before* you reboot and after removing udev.<br> ><br> > Removal of udev has caused a few (temporary) problems with useflags,<br> > because a few packages still depend directly on udev instead of the<br> > newer (!systemd ? udev) which means accept either one but not both.<br> > That will get fixed soon, I'm sure.<br> ><br> > The right way to upgrade gnome is probably to remove every gnome<br> > package on the machine, which will avoid many of the conflicts I've<br> > had to fight for the last two days -- but of course I did it the hard<br> > way instead :)<br> ><br> > You can try emerge -au gnome-light early in the update, which is<br> > simpler than emerging gnome in all its immensity, but that's no<br> > guarantee of success -- I'm sure you'll still run into conflicts<br> > between packages and useflags, but it might be a bit easier.<br> ><br> > When you see conflicting packages that won't install, I suggest<br> > deleting both packages immediately -- let portage sort out the<br> > conflicts. Just keep removing packages until portage finally<br> > stops complaining.<br> ><br> > Beware of pambase, however. I finally took Canek's advice and<br> > removed consolekit from the machine and unset the useflag for<br> > all packages, including pambase and polkit. I'd suggest you<br> > get pambase and polkit re-installed with the proper useflags<br> > before you try to reboot. Dunno if that's mandatory, but I did<br> > it that way and had no problems (yet).<br> ><br> > I've finished updating my virtual gentoo systemd machine now,<br> > but I'm still fighting with the virtual openrc machine and I'm<br> > not sure how it will turn out. More tomorrow :)</p> <p>I haven't upgraded yet to the last update (although I've been using GNOME 3+systemd for years), but I do know this: the primary reason of GNOME's dependency on systemd is logind, and logind *CANNOT* run correctly if systemd is not the running init.</p> <p>So you not only need to install systemd: you need to use it as init. I don't even think logind can start if systemd is not running.</p> <p>And actually, the long term plan is for systemd --user to basically replace gnome-session-manager, so just installing systemd is not going to work at all in the future, even if it *may* seems to work now (which I'm pretty sure it doesn't).</p> <p>systemd provides some pretty complex functionality for logind (and therefore GNOME) while running; it's not just some libraries.</p> <p>Regards.</p>