On Tue, Jun 20, 2017 at 06:10:05PM +0200, Michael Biebl wrote: > Hi Ron > > Am 20.06.2017 um 17:12 schrieb Ron: > > On Tue, Jun 20, 2017 at 02:48:02PM +0200, Michael Biebl wrote: > > >> If you are worried about backports: /bin/udevadm is already available in > >> Debian jessie (oldstable) or Ubuntu trusty (14.04LTS). So it's safe to > >> use the /bin/udevadm path. > > > > Unless I'm missing something it will break for Wheezy though, which is > > still an LTS maintained release for about another year? > > The udev version in wheezy ships udevadm as /sbin/udevadm indeed. > So if you plan backports to oldoldstable, you'd need to take that into > acount. > > And as an > > upstream part of the package, we do expect to be portable to other > > distros too - so I'd guess there's also things like RHEL releases where > > the old path might still be in use for quite some time to come? > > What you want to support from an upstream POV is of course your > decision. I can't really tell what other distros do tbh. > I would be suprised though, if faster moving distros, like Arch, which > are close to upstream, actually provide a /sbin/udevadm compat symlink > According to https://www.archlinux.org/packages/core/i686/systemd/ this > is not the case. > So your package is already broken there.
Ah, that's a good data point, thanks. We do have a user maintaining a package of this for Arch - but so far (aside from this bug) nobody has reported having a problem with it yet. But this is just in an example script, which is really only needed for people who want to hotplug devices into a libvirt managed VM, so that's probably not all that surprising (and someone will probably report it tomorrow now that we know :) Making it default to checking for both places definitely seems like the least-pain answer to run with then. Thanks, Ron
