How to Handle Packaging Plugins

Digging into drizzle over the last few days, and going through the process of stipping down plugins to the bare minimum needed to run drizzle... as well as packaging them all separately, I'm beginning to thinking that having a separate package for *every* plugin isn't the best approach. For one... because everything is a plugin... there are a large number of plugins that are expected to just be there enabled by default and would likely not be replaced by another plugin.

I think a good approach would be to split the deck as 'core plugins', and 'optional-not-everyone-would-want-this' plugins. I think the core plugins should be grouped under a single package... maybe even just grouped under 'drizzle-server'. The plugins that are packaged separately would be more of the specific use.

Example Core Plugins: multi_thread, single_thread, *_dictionary, auth_pam, connection_id, function_engine, schema_engine, etc

Example Optional Plugins: archive, blackhole, benchmark, csv, etc

In my mind 'plugins' just automatically trigger the need for a subpackage... but I think in drizzle case it doesn't fit for every plugin (really only a small set of plugins).