Hi,
On 5/27/24 22:18, Simon McVittie wrote:
So I think your syslogd-is-journald could not be a Provides on the
existing systemd-sysv package, and would have to be a separate package.
I'm not sure that the benefit is worth it (and I see that Luca is sure
that the benefit *isn't* worth it).
I agree -- that's why I suggested changing the dependency to
"systemd-sysv | system-log-daemon"
This does not require an extra package, leaves out the system-log-daemon
on most systems, still leaves the option of co-installing a flat logging
daemon parallel to journald, and the packages work out-of-the-box on
derived non-systemd distributions, so we don't waste developer time on
maintaining a fork just for this issue.
Along similar lines, I have wondered about
dbus-{system,session}-bus-is-external packages as non-default providers
of dbus-{system,session}-bus, for use in containers that arrange for a
suitable socket to be bind-mounted in from outside, but I'm unsure how
much appetite there is for a proliferation of packages whose metadata
is larger than their content for purposes like these - especially if
they could accidentally get installed (possibly on real systems rather
than in containers) by users who have not actually made the documented
arrangements, resulting in spurious bug reports and extra support burden.
Indeed, but we only have the two options "make it declarative in the
package namespace" and "make it an essential service that packages may
rely on without making a declaration."
The latter would imply that we'd need to officially state that using
Debian packages for Docker containers or inside CI runners is
unsupported, because these don't fulfill the requirements for essential
services.
Simon
