Hello, > So, the problem is that I don't have any numbers about which plugins are used most. > I would like to avoid (unless there's a really good reason for it) to handle some plugins > differently from the rest because that creates an inconsistent experience.
My suggestion here is to have separate collectd-core package with just core application and docs and several collectd-plugin-* (like collectd-plugin-disk) packages with just .so file and, if applicable, default config file in /etc/collectd/plugins.d subdir or something like that. Metapackage might install something that already enabled by default, like rrd, network etc, or might not install anything at all, allowing user to decide which ones to use. > The packages do not force the installation of any of the dependencies. > That's why there is collectd-core and collectd which provide different degrees of flexibility > by suggesting or recommending all plugin dependencies. Oh, I never tried to install just collectd-core, always thought I should use collectd package. > build your own meta-package which provides your custom configuration, the required > dependencies for that configuration and then depends on collectd-core. Currently, I end up with manual rebuilding the package, adding several --disable-plugin options to configure. At this point I've decided to create this thread. Best regards, Andrey -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
