Hi Holger, On Thu, Oct 23, 2008 at 12:12:08PM +0200, Holger Levsen wrote: > Hi, > > On Thursday 23 October 2008 10:51, Guido Günther wrote: > > I discussed that with Matthias and didn't come to conclusion. Finally I > > decided to go for an extra package. Basically for two reasons: > > > > * I don't have to bother you folks with new versions (there's already a > > forth plugin underway) > > 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.
> > * we don't need to add even more dependencies to munin-plugins-extra. > > Folks might not want to have python-libvirt which pulls in libvirt > > which pulls in xen libs on their system. > > Currently we only use suggests for stuff the plugins need... 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. > > > * Backports: backporting munin-plugins-extra will become hard if there > > it has too man dependencies > > See above :) > > > So here's my suggestion: let's let the plugins stabilize a bit while > > keeping them in an exrra source package and move them over to > > munin-plugins-extra then (maybe shipping them as an extra binary > > package, so people don't need install them). > > Are these plugins even automatically configured? The vserver ones are not and > I doubt these are. 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: VER=$(dpkg-query -W -f='${Version}' munin-node) if [ "$VER" ]; then munin-node-configure --families=contrib --shell --since $VER > $TMPFILE || true ... fi Cheers, -- Guido -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]