Bug#743941: marked as done (cups-daemon: why does cups-daemon depend on libsystemd-daemon0)
Your message dated Tue, 08 Apr 2014 18:38:39 +0200
with message-id <2680296.zCdV4p9xUJ@gyllingar>
and subject line Re: Bug#743941: cups-daemon: why does cups-daemon depend on libsystemd-daemon0
has caused the Debian Bug report #743941,
regarding cups-daemon: why does cups-daemon depend on libsystemd-daemon0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
743941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743941
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: cups-daemon
Version: 1.7.1-10
Severity: minor
Hi,
I just wanted to ask, why cups-daemon depends on libsystemd-daemon0?
I do not see why a daemon should depend on a specific init system.
And especially why it should polute my system with the libraries
of an init system i am not using.
Thanks for your time and greetings from Switzerland
Attila Kinali
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages cups-daemon depends on:
ii adduser 3.113+nmu3
ii bc 1.06.95-8
ii dpkg 1.17.6
ii init-system-helpers 1.18
ii libavahi-client3 0.6.31-4
ii libavahi-common3 0.6.31-4
ii libc6 2.18-4
ii libcups2 1.7.1-10
ii libcupsmime1 1.7.1-10
ii libdbus-1-3 1.8.0-3
ii libgnutls26 2.12.23-13
ii libgssapi-krb5-2 1.12.1+dfsg-1
ii libpam0g 1.1.8-2
ii libpaper1 1.1.24+nmu2
ii libsystemd-daemon0 204-8
ii lsb-base 4.1+Debian12
ii procps 1:3.3.9-2
ii ssl-cert 1.0.33
Versions of packages cups-daemon recommends:
pn avahi-daemon <none>
ii colord 1.0.6-1
pn cups-browsed <none>
Versions of packages cups-daemon suggests:
ii cups 1.7.1-10
ii cups-bsd 1.7.1-10
ii cups-client 1.7.1-10
ii cups-common 1.7.1-10
ii cups-filters [foomatic-filters] 1.0.50-1
pn cups-pdf <none>
ii cups-ppdc 1.7.1-10
ii cups-server-common 1.7.1-10
ii foomatic-db-compressed-ppds [foomatic-db] 20140325-1
ii ghostscript 9.05~dfsg-8+b1
ii hplip 3.14.1-1
ii poppler-utils 0.22.5-4+b1
ii printer-driver-gutenprint 5.2.9-1
ii printer-driver-hpcups 3.14.1-1
ii smbclient 2:4.1.6+dfsg-1
ii udev 204-8
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Attila, and thanks for your question.
Le mardi, 8 avril 2014, 17.43:27 Attila Kinali a écrit :
> I just wanted to ask, why cups-daemon depends on libsystemd-daemon0?
cups-daemon _can_ make use of systemd-specific socket activation when
launched on a system which has systemd as init; in which case it is only
launched for 30 seconds when needed and stays off the rest of the time.
That codepath is _not_ used under other inits (in fact, the patch we
picked is specifically aimed at supporting multiple inits at runtime).
So, formulated differently: the dependency on libsystemd-daemon0 is a
convenience for the benefit of those using systemd as init but is not at
all a dependency on a specific init system.
> I do not see why a daemon should depend on a specific init system.
It doesn't.
> And especially why it should polute my system with the libraries
> of an init system i am not using.
libsystemd-daemon0 has no dependencies besides libc6 and currently
weighs 68k of diskspace (libcups2 is 605k, libcupsimage2 is 130k). If
that's a problem, equivs can let you create a replacement package for
less diskspace.
Given that this will not change (especially not given the recent
decision to use systemd as default init system), I'm hereby closing this
bug.
> Thanks for your time and greetings from Switzerland
Greetings from a swiss train!
Cheers, OdyX
--- End Message ---
Reply to: