Hi tito,

On Fri, 2023-07-28 at 22:20 +0200, tito via Dng wrote:
> Hi,
> A new, official systemd release (254) has just been tagged:
>
>  * Support for System V service scripts is now deprecated and will be
>    removed in a future release. Please make sure to update your
> software
>    *now* to include a native systemd unit file instead of a legacy
>    System V script to retain compatibility with future systemd
> releases.
>
> A wonderful excuse to remove the last init scripts from packages.
>
Since when has systemd had any authority over anyone but systemd?

I can see that the systemd developers can ask that developers of daemon
programs include a systemd service file but surely they have no
authority to insist that developers not include sysV or runit scripts
for packaging if they so choose?

Though I suppose that MS or Redhat developers would have to comply.

As to how we fill in the gaps - obviously we already have orphan-
sysvinit-scripts - we also have sysd2v.sh
( https://github.com/RosstheRoss/sysd2v/blob/main/README.md and
https://git.savannah.nongnu.org/cgit/sysvinit.git/tree/contrib/sysd2v.sh
)
which can generate sysVinit scripts from simple systemd service files.

I wouldn't suggest we could use the latter to generate init scripts on
the fly but it could be used to add scripts to
orphan-sysvinit-scripts once they had been tested.

The other need is to patch the affected debs so that the relevant
sysvinit init, preinst, postrm, preinst, prerm scripts are included,
albeit this can be easily automated.

How many daemons are there? I have 76 init files in my /init.d.

--
Marjorie