Hi, On Mon, Jan 13, 2014 at 04:19:59AM +0400, Andrey wrote: > > Recommends / Suggests only includes dependencies of actual plugins. > > C'mon, it's about 200 Mbytes of unneeded libraries, like tokyotyrant or > varnish, or libvirt etc, not counting full jdk installation and others, > which most users won't need.
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. The user would then have to know whether or not a plugin has external dependencies and whether those dependencies are "usual" or not. So for, nobody (including myself) had a real answer to that. > I'm trying to use collectd in virtual > environment with puppet system rollout which means that each virtual > machines downloads 200 Mbytes on start. If you build it manually, at least > you have an option to not to include unneeded plugins. This package forces > user to install them. Check other big packages like php or python. They are > broken into many pieces so I can install only needed ones. 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. The solution I have in mind for cases like yours is to either disable installation of recommended packages and then use the collectd package or to build your own meta-package which provides your custom configuration, the required dependencies for that configuration and then depends on collectd-core. HTH, 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
