[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Package tool with systemd dependency

On Tue, 2016-06-21 at 10:55 +0100, Simon McVittie wrote:
> On Tue, 21 Jun 2016 at 11:11:09 +0200, Jan Luca Naumann wrote:
> > I want to package a tool* which highly uses systemd and particulary
> > its
> > per-user service feature.
> By "per-user service" are you referring to systemd user services,
> which are
> children of the per-user service manager, "systemd --user"
> (aka the system service user@.service, started by systemd-logind)?

The upstream repository looks like it provides .service units for a
"systemd --user" instance.

> You should probably use Depends: libpam-systemd (which means you
> get a working systemd-logind somehow, either via systemd-sysv or
> sysvinit + systemd-shim) together with a Depends or Recommends on
> systemd-sysv. That's what I did for dbus-user-session.

AFAIK this is not enough to get a "systemd --user" instance. You would
need to depend on both libpam-systemd *and* systemd-sysv.

That said I think packages should avoid depending on systemd-sysv if
possible. It should be fine to only provide a unit for "systemd --user" 
and people who don't use systemd or libpam-systemd then have to
configure the service start and stop themselves.


Reply to: