sys-fs/udev depends on sys-fs/udev-init-scripts. All the files installed by sys-fs/udev-init-scripts (with the possible exception of 40-gentoo.rules) are redundant to a Gentoo machine running with systemd. Being able to optionally not install sys-fs/udev-init-scripts would be nice; perhaps with a "+openrc" USE flag, set by default. Reproducible: Always
The only reason I am hesitating on this bug is /etc/modprobe.d/blacklist.conf. Do systemd systems need this file?
(In reply to comment #1) > The only reason I am hesitating on this bug is > /etc/modprobe.d/blacklist.conf. Do systemd systems need this file? I don't think so. systemd depends on udev, and new versions of udev on kmod, and kmod man pages have no mention of "blacklist.conf". In fact, the only reference in kmod to blacklists is (I believe) in the context of aliases for modules. From the man page of modprobe.conf: "blacklist modulename Modules can contain their own aliases: usually these are aliases describing the devices they support, such as "pci:123...". These "internal" aliases can be overridden by normal "alias" keywords, but there are cases where two or more modules both support the same devices, or a module invalidly claims to support a device that it does not: the <command>blacklist</command> keyword indicates that all of that particular module's internal aliases are to be ignored." These blacklists can be specified in any *.conf file inside /etc/modprobe.d. I myself am not using /etc/modprobe.d anymore.
This has been fixed in udev-182.
