It seems like workarounds for this bug are being merged into mir, even though on all ubuntu releases libudev.pc has been corrected to point at the right location for the libudev.so.
E.g.:
cat /usr/lib/x86_64-linux-gnu/pkgconfig/libudev.pc
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
It seems like workarounds for this bug are being merged into mir, even though on all ubuntu releases libudev.pc has been corrected to point at the right location for the libudev.so.
E.g.:
cat /usr/lib/ x86_64- linux-gnu/ pkgconfig/ libudev. pc
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
prefix=/usr /lib/x86_ 64-linux- gnu /usr/include
exec_prefix=/usr
libdir=
includedir=
Name: libudev
Description: Library to access udev device information
Version: 232
Libs: -L${libdir} -ludev
Cflags: -I${includedir}
(zesty- amd64)root@ sochi:/ tmp# dpkg -S libudev.so 64-linux- gnu/libudev. so.1.6. 5 64-linux- gnu/libudev. so 64-linux- gnu/libudev. so.1
libudev1:amd64: /lib/x86_
libudev-dev:amd64: /lib/x86_
libudev1:amd64: /lib/x86_
This is results for zesty.
Thus no workarounds should be needed at all in the mir scripts.