tools/ci-build.sh overwrites installed systemd files when using ci_sudo=yes
While looking at !425 (merged) I recognized that building with meson on an openSUSE system with
$ builddir=ci-build ci_sudo=yes ci_buildsys=meson tools/ci-build.sh
overwrites existing files from the installed dbus-1 package:
Installing /home/xxx/src/dbus/ci-build/bus/dbus.service to /usr/lib/systemd/system
Installing /home/xxx/src/dbus/ci-build/bus/dbus.socket to /usr/lib/systemd/system
...
Installing /home/xxx/src/dbus/ci-build/bus/systemd-user/dbus.service to /usr/lib/systemd/user
Installation of /home/xxx/src/dbus/ci-build/bus/systemd-user/dbus.socket to /usr/lib/systemd/user
...
Installation of a symlink on ../dbus.service to /usr/lib/systemd/system/multi-user.target.wants/dbus.service
Installing a symlink pointing to ../dbus.socket to /usr/lib/system/system/sockets.target.wants/dbus.socket
Installing a symlink pointing to ../dbus.socket to /usr/lib/system/user/sockets.target.wants/dbus.socket
This can work on a container or in a VM, but not on a local host.
On https://unix.stackexchange.com/questions/224992/where-do-i-put-my-systemd-unit-file a tool called systemd-analyze unit-paths
is mentioned that returns /usr/local/lib/systemd/system
among other directories, which I think would be usable in this case.