Hi, On Fri, Aug 22, 2008 at 10:45:05AM +0200, Marc Fargas wrote: > Just wondering, maybe moving the rrdtool plugin to its own package > (Suggested by collectd) would do the job?
No. Then the default installation would not provide any useful functionality. The same could be achieved by moving librrd from Depends: to Recommends: (just like for any other plugin with external dependencies) but I did not do that for exactly the same reason. The only sane way to implement this is to have two packages (e.g. "-server" and "-client") which conflict each other and provide different configurations each (i.e. either rrdtool or network enabled). They would both need the collectd binary and the plugins, so that would probably have to be split out into an extra package (e.g. "-core") so that we don't have to ship that twice. "-server" and "-client" would both depend on that. The "collectd" package would then only be a dummy package depending on "-server" (i.e. the one with rrdtool enabled), I guess. Imho, this is the more reasonable default and preserves the "semantics" on upgrades. Any thoughts? Cheers, Sebastian -- Sebastian "tokkee" Harl +++ GnuPG-ID: 0x8501C7FC +++ http://tokkee.org/ Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin
signature.asc
Description: Digital signature
