On Sat 29/Jul/2023 12:33:28 +0000 Tito wrote:
> On Sat, 29 Jul 2023 21:23:27 +1000
> onefang <onefang_devuan@???> wrote:
>> On 2023-07-29 08:13:22, tito via Dng wrote:
>>> On Sat, 29 Jul 2023 14:30:36 +1000
>>> onefang <onefang_devuan@???> wrote:
>>>> On 2023-07-29 08:18:54, Alif Radhitya Wardana wrote:
>>>>> Based on this changelog, what will happen in the future to SysV? I mean,
>>>>> if systemd forces people to create native systemd units, will people drop
>>>>> sysv scripts on their apps?
>>>>>
>>>>> A wonderful excuse to remove the last init scripts from packages.
>>>>
>>>> Do I have to resurrect my ancient LSB compliant SysV init code that could
>>>> figure out dependencies, run things in parallel, and even work with init
>>>> "scripts" written in ANY language? [...]
>>>>
>>>> I could teach it how to grok shitsemDie units.
>>>
>>> yes using the info contained in .service units would be
>>> a elegant solution, [...]
>>
>> If I ever go ahead with this, I'll figure it out.
>
> I think this is the only way to stay ahead of systemd devs
> using their own momentum. Init scripts are the preferred
> tool to marginalize other init systems as you have to ship
> them yourself for every daemon out there, using service
> files to get the info and rebuild init scripts on the fly
> at first boot would be such a masterpiece!


Building on the fly on the first boot won't work for those who want to run
the daemon right after installing, without booting.

I'd prefer the script to be included in the package when I install, which I
hope will be continued for Devuan repositories.


Best
Ale
--