[Dev] general procedure for adding nonsystemd init scripts

Freemor freemor at freemor.ca
Sat May 2 11:05:58 GMT 2020

On Sat, May 02, 2020 at 02:24:19AM -0400, bill-auger wrote:
> we often get requests for init scripts, for some service that is
> not working with openrc - have we converged on a convention for
> how to add them?
> surely there are different ways it could be handled; but it
> would be best if they were all done consistently
> should they all go together in single package like
> 'nonsystemd-init-scripts', or should each be a separate package
> like 'foo-init-scripts'?
> _______________________________________________
> Dev mailing list
> Dev at lists.parabola.nu
> https://lists.parabola.nu/mailman/listinfo/dev

Unless things have changed drastically since the last time I looked the
*-openrc init scripts are created by the openrc package (which is a large split
package). Probably the best approach for missing ones would be to create the
missing one(s) add them to that package then push the patches upstream, So that
other distros that support openrc get them as well.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20200502/92025d5f/attachment.sig>

More information about the Dev mailing list