On Sun, Sep 4, 2011 at 12:32 PM, Michael Shigorin <m...@osdn.org.ua> wrote: > > It's nice in general, but when packaging, it tends to result > in "alternative builds". I do understand that it's probably > not your objective, but knowing this can make further work > in this direction easier. > > The problem is that as far as I can tell, the 5.2.x branch doesn't have any sort of plugins infrastructure, and adding one to Monit is really not in the scope of what I intend to do.
An IPC infrastructure is also problematic for me, since it means I can't use the IPC infrastructure already written by the NetSNMP project (the AgentX code), and instead I have to roll my own. > > Is this sufficient? > > For me to enable it in ALT Linux package by default, no. > But I'll make a build-time %define knob too, of course. > That would be great. I'll set the default to disable SNMP support, so existing packages would not be affected. > Guess Debian or OpenWall folks might think similarly. > In Debian, there are source packages that generate multiple binary packages that are configured and built a bit differently. It should be possible for the source package to generate a "monit" binary package that is compiled without snmp, and a "monit-snmp" binary package that does provide snmp support. The user would have to choose the required package according to the deployment needs. Lior
_______________________________________________ monit-dev mailing list monit-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/monit-dev
