ProwlerGr
Great initiative @anticapitalista
My stuff should all be on Gitlab under:
https://gitlab.com/init-diversity
I’ll just give you a rundown of what I have done for each init:
Sysvinit:
Nothing really, just using the already provided scripts
OpenRC:
The same, I have provided this as an init just because it works
Runit:
I have created a template deb package under runit-service-xxxxx
– Replacing xxxxx with the <service-name> in all text-files & maintainer scripts
– Renaming override-sysv.d/xxxxx.block to <service-name>.block (this stops the sysvinit service scripts from running)
– Replacing the contents of the services folder, with the proper runit service files
Would get the initial package up & running subject to final fine adustments (regarding dependencies)
Dinit:
Very similar workflow with template deb under dinit-service-xxxxx
– Replacing xxxxx with the <service-name> in all text-files & maintainer scripts
– Typically the config & scripts folders would be deleted (only used occassionaly on complex services)
– Replacing the contents of the services folder, with the proper dinit service files
Would get the initial package up & running subject to final fine adustments (regarding dependencies)
s6-66:
This is a bit different, but I have found a method to automatically convert Obarun’s packaging to debs using quilt.
A big number of services has already been converted, I am happy to continue helping to convert the rest as this is my primary init of interest.
Packaging template under 66-service-xxxxx.
s6-rc:
Template deb under s6-rc-service-xxxxx with similar logic to runit & dinit
- This reply was modified 1 year, 4 months ago by ProwlerGr.
- This reply was modified 1 year, 4 months ago by ProwlerGr. Reason: Formatting
- This reply was modified 1 year, 3 months ago by ProwlerGr. Reason: 66-service-xxxxx packaging template provided