On Thu, Oct 30, 2008 at 12:30:26PM +0100, Holger Levsen wrote: > Hi Guido, > > no need to cc: Matthias or me, we are subscribed to the bug :) I meant to drop the bugreport from cc: (since this is becoming a bit OT) but obvously forgot about it.
> On Wednesday 29 October 2008 10:07, Guido Günther wrote: > > > I guess we would happily welcome you in the munin maintainer team :-D > > Thanks, but I don't think I'd be of much help. I can sponsor Matthias > > uploads should you be short on time though. > > Thanks. (The only reason I can imagine you wouldnt be of help is due to lack > of time. I guess you mean that ;) ...and a lack of perl skills... > > > That's what I'm a bit afraid of, I want the plugins to just work without > > the user having to figure out what else he needs. This becomes more > > important the more packages get added to munin-plugins-extra. s/more package/more plugins/ > > Right. And this is also something I dont like. Not sure how to solve it > though... (we could build more plugin binary packages in future...) Yes, more binary packages (with strict dependencies) would make sense. This way we could fold the libvirt plugins into the package easily and things like detecting if a plugin makes sense to be installed wouldn't bloat the one and only postinst. Folding all the contrib plugin into their own source package so they can be maintained independelty of munin intself would probably make sense too. Having e.g. the whole vserver plugin as a patch feels strange and makes modifying it harder as it should be. > > They don't need any configuration for most of the cases. I'm not > > creating the symlinks though yet since I wanted to check back with you > > about the best way to do it. I'd to this in the postinst: > > Do you check if virtualisation is enabled? Used? Trying the supported hypervisors: virsh --connect xen:/// list virsh --connect qemu:///system list does the trick here. -- Guido -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
