[nut-Patches][313927] systemd system unit dir is mangled by configure script

[nut-patches at alioth.debian.org]

nut-Patches item #313927, was opened at 2012-12-16 10:33 by Calvin Walton
You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detail&atid=411544&aid=313927&group_id=30602

Status: Open
Priority: 3
Submitted By: Calvin Walton (kepstin-guest)
Assigned to: Nobody (None)
Summary: systemd system unit dir is mangled by configure script 
Category: None
Group: None
Resolution: None


Initial Comment:
I'm building nut with the following configuration options in a package:

./configure --prefix=/usr --libdir=/usr/lib64 --with-systemdsystemunitdir=/usr/lib64/systemd/system [...]

However, the systemd units are actually being installed to the path "/usr/usr/lib6464/systemd/system" instead of the requested "/usr/lib64/systemd/system". I've traced this down to the line in configure.in that says:

systemdsystemunitdir="`echo ${systemdsystemunitdir} | sed 's/\/lib/\${libdir}/'`"

which is obviously not correct in general. There's a note about this fixing 'make distcheck' somehow, but I don't see how this change is relevant... If files are being written to the real root during distcheck, that's a makefile installation rule bug, not a reason to mangle user-provided paths.

I'm currently testing the trivial patch, attached.

(As an aside, systemd does install pkg-config files, and it wouldn't be hard to add some user-friendly autodetection to nut's configure script. Note that "pkg-config --variable=systemdsystemunitdir systemd" will print the correct installation path.)

----------------------------------------------------------------------

You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detail&atid=411544&aid=313927&group_id=30602