Hello,
I'm interested in extending the svc module for nosh (and possibly other
daemontools family toolsets) and have a couple of questions/observations.
A. current svc extension issues
I initially wrote the svc module with those extensions in mind, but
the runit was done as a copy instead ... im fine with refactoring to
fix this or just create a set of modules that deal with each fork.
As for 'service', the module itself is deprecated, its now an 'action
plugin' which chooses the underlying module to execute. This still
relies on autodetection but can also be done via a `use` option to
force a specific module, basic options must be compatible with service
though.
Hello,
I initially wrote the svc module with those extensions in mind, but
the runit was done as a copy instead ... im fine with refactoring to
fix this or just create a set of modules that deal with each fork.
Ok great, I'll try extend via the svc module then.
For the subclassing mechanism, because the Svc class is only used with
`svc = Svc(module)`, I simplified the signature to:
_load_dist_subclass(cls, module)
So that one can then just assign `distro` like this:
distro = module.params['distro']
Incidentally, is there any preference between calling that parameter
"distro" or "dist"? Or something else like "manager"?
As for 'service', the module itself is deprecated, its now an 'action
plugin' which chooses the underlying module to execute. This still
relies on autodetection but can also be done via a `use` option to
force a specific module, basic options must be compatible with service
though.
Thanks, I will look at that.
Regards,
taca
Use whatever name makes the most sense.