There are sufficient users of zmNinja's zmeventnotitication daemon at this stage. Billions!!!!!millions!!!!hundreds of thousands!!!tens of thousands!!thousands! few hundred likely.
Problem Statement:
Every time ZM is updated, the notification server gets removed from zmdc and zmpkg as its currently a manual process.
The issue with packaging the daemon is it relies on certain libraries that need some manual exploring to figure out the exact names depending on distro. I only maintain a ubuntu guide and I leave it to users to figure it out for others.
Proposed Approach:
While chatting with @connortechnology on IRC, we talked about making this an optional element.
My thought is this:
a) We list it as a OPT_USE_XXXX in options. We add a help text saying please install this separately from my repo manually
b) We add conditional code in zmdc.pl and zmpkg.pl to add it to the lists if enabled. It is the user's responsibility to make sure the daemon is actually present.
If this is acceptable, I'll do a PR in a few days.
There are sufficient users of zmNinja's zmeventnotitication daemon at this stage.
Billions!!!!!millions!!!!hundreds of thousands!!!tens of thousands!!thousands!few hundred likely.Problem Statement: Every time ZM is updated, the notification server gets removed from zmdc and zmpkg as its currently a manual process.
The issue with packaging the daemon is it relies on certain libraries that need some manual exploring to figure out the exact names depending on distro. I only maintain a ubuntu guide and I leave it to users to figure it out for others.
Proposed Approach: While chatting with @connortechnology on IRC, we talked about making this an optional element.
My thought is this: a) We list it as a OPT_USE_XXXX in options. We add a help text saying please install this separately from my repo manually b) We add conditional code in
zmdc.plandzmpkg.plto add it to the lists if enabled. It is the user's responsibility to make sure the daemon is actually present.If this is acceptable, I'll do a PR in a few days.