I had the idea of maybe keeping the sysV file (if someone wants it for odd setups), but trying to spread --no-start all over the place to hopefully reach a situation where the .socket but nothing else is started on install/upgrade.
Therefore it would be less invasive, but still achieve what we want.
See [1] for a branch with that.
But as I experienced in the past, it does not start the socket then.
dh_installinit section does only update (as intended):
update-rc.d ibacm defaults
but dh_installsystemd takes over the --no-start and ends up calling "deb-systemd-helper update-state 'ibacm.socket'" twice.
The last option would be to manually code the snippets correctly to have:
- sysV init installed but not started
- .service installed but not started
- .socket installed and started
Hrm, that should be a common case - I'm getting more and more sure I'm missing something ...
I'll compare a few other packages.
I had the idea of maybe keeping the sysV file (if someone wants it for odd setups), but trying to spread --no-start all over the place to hopefully reach a situation where the .socket but nothing else is started on install/upgrade.
Therefore it would be less invasive, but still achieve what we want.
See [1] for a branch with that.
But as I experienced in the past, it does not start the socket then.
dh_installinit section does only update (as intended):
update-rc.d ibacm defaults
but dh_installsystemd takes over the --no-start and ends up calling "deb-systemd-helper update-state 'ibacm.socket'" twice.
The last option would be to manually code the snippets correctly to have:
- sysV init installed but not started
- .service installed but not started
- .socket installed and started
Hrm, that should be a common case - I'm getting more and more sure I'm missing something ...
I'll compare a few other packages.
[1]: https:/ /github. com/cpaelzer/ rdma-core/ tree/debian- avoid-unconditi onal-ibacm- start-noremove