I migrated to systemd recently and realized that google-chrome was not starting after that. The message is: google-chrome-stable /usr/bin/google-chrome-stable: error while loading shared libraries: libudev.so.0: cannot open shared object file: No such file or directory Because systemd have its own udev implementation. However, despite the fix is simply re-emerging google-chrome again, I did not see anything regarding that, and can cause confusion. I suggest to put it on preserved rebuild list, or to mention it in news after emerging systemd to inform users that it have to be rebuild. Or even better, when installing systemd (mainly for first time), add google-chrome to the emerge list to avoid it failing.
When google-chrome is installed with udev, you will have the following symlink: /opt/google/chrome/libudev.so.0 -> /lib64/libudev.so.1 When systemd is installed, /lib64/libudev.so.1 will be moved to /usr/lib64/libudev.so.1. This will break the /opt/google/chrome/libudev.so.0 symlink, until it is recreated by pkg_postinst. This could be avoided if sys-apps/systemd installed libudev in the same place as sys-fs/udev.
I suppose I could go back to abusing the /usr/lib/libudev.so symlink, as this was originally implemented. In theory, that link should always be valid on a Gentoo system with udev or systemd installed.
I'm going to leave this as-is.
