>> Okay, I understand your reasons. It would just be nice to say: on this >> host I additionally install collectd-rrdtool, it starts writing rrd >> files out of the box and the whole dependency mountain gets cleaned away >> if I change my mind and uninstall it. > > Hrm … the only way, I can think of, to implement that, would be to > introduce a new binary package for each plugin (with external > dependencies). See my previous E-mail, why I do not want to implement > that. Any other ideas how to do that would be very appreciated. >
How about following apache2's model ? Have collectd package with the most used plugins like mem/cpu/disk/etc bundled in and have either a collectd-extra package or multiple collectd-foo for different plugins. Same for directory structure - I really like de mods-available/mods-enabled thing. Regards _______________________________________________ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
