On 10/12/2018 01:56 AM, KatolaZ wrote:
> On Thu, Oct 11, 2018 at 11:55:29PM -0400, Steve Litt wrote:
>> On Fri, 12 Oct 2018 03:24:44 +0000
>> alecfeldman@??? wrote:
>>
>>
>>> 1. Split the runit package into separate packages with alternate
>>> stage files.
>>>
>>> 2. Provide a configuration file for how runit should act. For
>>> instance, if openrc or sysvinit is installed, runit can depend
>>> on /etc/init.d and /etc/rc*.d scripts for booting.
>>
>> On a related note, I think the best way of acquiring runit run files is
>> to install Void Linux on a VM, install all the various daemons, and
>> then view the run files in /etc/sv/$daemonname/run.
>>
>> Void has had enough time supporting runit that most of their run files
>> work great. The exceptions usually assume device names that shouldn't
>> be assumed.
>>
>> Devuan could thus acquire a whole bunch of run scripts and not have to
>> beg the upstreams to do it.
>>
>
> The main problem remains how to distribute those scripts, without
> having to fork all the packages that provide a runit script and don't
> have one in the corresponding Debian package. Any concrete proposal is
> welcome there (but I know that most of the simple ones won't work,
> since people willing to use runit want their preferred service to work
> ootb and already have runit scripts, and only when they install that
> specific server...).
>
> Also, we are not just talking of supporting either openrc or runit,
> but to add support for runit *on top* of sysvinit and openrc.
>
> We should definitely find a way through, but I can't see the optimal
> one at the moment :\
>
> My2Cents
>
> KatolaZ


Why not a meta-package including all packages for each init?
--
Jimmy Johnson

Slackware64 14.2 - KDE 4.14.32 - AMD A8-7600 - EXT4 at sda9
Registered Linux User #380263