#13748 closed enhancement (wontfix)
dbus installes systemd files in SysV
Reported by: | thomas | Owned by: | thomas |
---|---|---|---|
Priority: | normal | Milestone: | 10.0 |
Component: | BOOK | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: |
Description ¶
The options --with-systemduserunitdir=no
and --with-systemdsystemunitdir=no
are meant to disable the installation of systemd service files. Unfortunatly, the are installed anyway. Furthermore, the 'no' of this options leads to a creation of a garbage directory when using the DESTDIR installation method.
Easiest way to overcome is to let the systemd stuff be installed and remove it after installation and remove the two --with-systemdXXXXunitdir options.
rm -rf $DESTDIR/usr/lib/systemd
and for direct installation (as used in book):
rm -rf /usr/lib/systemd
Change History (6)
comment:1 by , 5 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 5 years ago
comment:3 by , 5 years ago
I am not sure the premise of this ticket is correct. I used:
./configure --prefix=/usr \ --sysconfdir=/etc \ --localstatedir=/var \ --enable-user-session \ --disable-doxygen-docs \ --disable-xml-docs \ --disable-static \ --with-systemduserunitdir=no \ --with-systemdsystemunitdir=no \ --docdir=/usr/share/doc/$PROGRAM \ --with-console-auth-dir=/run/console \ --with-system-pid-file=/run/dbus/pid \ --with-system-socket=/run/dbus/system_bus_socket make make DESTDIR=$DEST install
Where PROGRAM=dbus-1.12.20 and DEST=/build/dbus/install.
What I ended up with is:
$ ls -l /build/dbus total 12 drwxr-xr-x 10 bdubbs bdubbs 4096 Jul 4 14:34 dbus-1.12.20 drwxrwxr-x 5 bdubbs bdubbs 4096 Jul 4 14:34 install drwxrwxr-x 3 bdubbs bdubbs 4096 Jul 4 14:34 installno
The installno directory has:
$ ls -lR installno installno: total 12 -rw-r--r-- 1 bdubbs bdubbs 360 Jul 4 14:34 dbus.service -rw-r--r-- 1 bdubbs bdubbs 178 Jul 4 14:34 dbus.socket drwxr-xr-x 2 bdubbs bdubbs 4096 Jul 4 14:34 sockets.target.wants installno/sockets.target.wants: total 0 lrwxrwxrwx 1 bdubbs bdubbs 14 Jul 4 14:34 dbus.socket -> ../dbus.socket
so if you are doing a DESTDIR install, not using installino means that the the systemd files are not installed, which is what we want.
comment:4 by , 5 years ago
Resolution: | → wontfix |
---|---|
Status: | assigned → closed |
The 'no'-dir in dbus appears as ${DESTDIR}no when using destdir-install - see previous comments.
Otherwise it is created somewhere within the source-dir (./bus/no) and therefore it is not installed on the destination file system.
Using 'no' as the pathnames prevents from installing the files on the filesystem, which means the original meaning of the options is met.
(Closing the ticket)
See also #13753 (new version with security fix)