Summary: | Migrating from sys-fs/udev to sys-apps/systemd temporarily breaks /opt/google/chrome/libudev.so.0 symlink | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | David Carlos Manuelda <StormByte> |
Component: | Current packages | Assignee: | Chromium Project <chromium> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | systemd |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
David Carlos Manuelda
2014-06-08 16:47:56 UTC
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. |