Am 22.02.2016 um 20:37 schrieb Niels Thykier: > On Fri, 04 Jan 2013 12:38:31 +0100 Luca Capello <l...@pca.it> wrote: >> Package: debhelper >> Version: 9.20120909 >> Severity: wishlist >> File: /usr/bin/dh_installudev >> Usertags: debian-packaging >> >> Hi there! >> >> When a package installs udev rules, these not automatically applied if >> the device is built-in (like fingerprint readers), since it is never >> plugged in (obviously, except if the computer is rebooted). Thus >> package.postinst must call `udevadm trigger` according to the udev's >> maintainer's explanation at: >> >> <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683863#27> >> >> While `udevadm trigger` could be called without options, IMHO it is >> preferable to limit its call(s) for the device(s) the package supports. >> In some cases, the number of the devices can be quite a lot (e.g. >> libfprint0 supports 17 of them), thus having an automatic way to >> generate these calls from the udev rules would be preferable. >> >> I would be glad to provide a patch, but I am a bit busy ATM. >> >> Thx, bye, >> Gismo / Luca >> >> [...] > > Hi systemd/udev maintainers, > > Is this something we can solve by using dpkg file triggers (or an > activate-noawait trigger)?
"udevadm trigger" should not be run unconditionally as it can have side effects. If it has to be run at all, it should be limited to packages which need it and be done for the corresponding subsystem only. So I think neither having dh_installudev generate that by default nor having a dpkg (file) trigger is a good idea. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
