Luke Diamand:
Are there any plans to create a debian package that would just put all
the bits in the right place, so you can simply install the package and
have it then use runit-init as /sbin/init ?
It's called runit-run, created over a decade ago, and it was a Debian
package for some years
Laurent Bercot:
I'm of the opinion that packagers will naturally go towards what gives
them the less work, and the reason why supervision frameworks have
trouble
getting in is that they require different scripting and organization, so
supporting them would give packagers a lot of work; whereas
Avery Payne:
But from a practical perspective there isn't anything right now that
handles
dependencies at a global level.
Now you know that there is.
The nosh design is, as you have seen, one that separates policy and
mechanism. The service-manager provides a way of loading and unloading
John Albietz:
I wonder if this will help address a common situation for me where I
install a package and realize that at the end of the installation the
daemon is started using upstart or sysv.
At that point, to 'supervise' the app, I first have to stop the current
daemon and then
Laurent Bercot:
Readiness notification is hard: it needs support from the daemon
itself, and most daemons are not written that way.
Ah yes. That reminds me. I said a while back that I have to give some
of you some good news.
https://lists.debian.org/debian-devel/2014/10/msg00709.html
On 1/19/2015 2:31 PM, Jonathan de Boyne Pollard wrote:
Avery Payne:
* implement a ./wants directory. [...]
* implement a ./needs directory. [...]
* implement a ./conflicts directory. [...]
Well this looks familiar.
I ducked out of ./needs and ./conflicts for the time being; if I spend
On 01/19/15 17:41, Laurent Bercot wrote:
On 19/01/2015 01:04, Olivier Brunel wrote:
Sure; though I'm totally fine if you want to discuss them, or would like
me to fix/make changes and re-send, as you see fit. That's what I
expected really.
I have implemented your suggestions, with minor
