sys-power/nut installs own systemd service files into /usr/usr/lib64/systemd/system/ instead of /usr/lib64/systemd/system/ $ qlist sys-power/nut | grep -i systemd /usr/usr/lib64/systemd/system/nut-monitor.service /usr/usr/lib64/systemd/system/nut-driver.service /usr/usr/lib64/systemd/system/nut-server.service /usr/lib64/systemd/system-shutdown/nutshutdown Reproducible: Always Steps to Reproduce: 1. emerge sys-power/nut 2. qlist sys-power/nut | grep -i systemd 3.
Created attachment 354488 [details] emerge --info
configure --help: --with-systemdsystemunitdir=DIR Directory for systemd service files (auto)
Sounds like it goes nuts :). configure.in:985 dnl Override installation directory, with the local installation dnl prefix. This is needed for 'distcheck*' targets, otherwise dnl files will try to get intalled to the actual system directories if test -n "${systemdsystemunitdir}"; then systemdsystemshutdowndir="${libdir}/systemd/system-shutdown" AC_MSG_RESULT(using ${systemdsystemunitdir}) systemdsystemunitdir="`echo ${systemdsystemunitdir} | sed 's/\/lib/\${libdir}/'`" else AC_MSG_RESULT(no) fi This is what screws it up hard. It's basically using pkg-config then assuming it gave a pre-defined value. And they're using that to hack distcheck over... Instead, they should add something like the following to Makefile.am's DISTCHECK_CONFIGURE_FLAGS (like they're doing e.g. for udev): --with-systemdsystemunitdir=\$${libdir}/systemd/system Would you proxy this upstream or shall we do it?
InCVS
