Bug#941198: initscripts: packages should ship systemd units
On Sun, Sep 29, 2019 at 03:19:43PM +0100, Josh Triplett wrote:
> On Sun, 29 Sep 2019 12:03:11 +0200 Bill Allombert <ballombe@debian.org> wrote:
> > On Sat, Sep 28, 2019 at 06:02:52PM -0700, Russ Allbery wrote:
> > > Sean Whitton <spwhitton@spwhitton.name> writes:
> > >
> > > > I don't currently have any reason to doubt we have a project consensus
> > > > that systemd unit files should be included in packages in addition to
> > > > sysvinit scripts, so I hope we can make this change.
> > >
> > > I agree. This seems entirely reasonable to me. Both the behavior and the
> > > inherent documentation are better with unit files, and systemd is the
> > > default init system so that's an advantage for a lot of our users.
> > >
> > > That said, if anyone does object to this, please do speak up and explain
> > > why this would be a problem.
> >
> > There is a little technical detail that should be handled though:
> > User might have made change to /etc/default/xxx that is sourced
> > by /etc/init.d/xxx.
> >
> > Such change must not be ignored by the unit files, because we require
> > configuration to be preserved across upgrade.
>
> I've seen multiple packages handle this through maintainer scripts that
> migrate (non-default) settings from /etc/default to a systemd drop-in or
> similar configuration file.
Could you explain how they proceed ? That might help.
Cheers,
--
Bill. <ballombe@debian.org>
Imagine a large red swirl here.
Reply to: