New comment by ailiop-git on void-packages repository

https://github.com/void-linux/void-packages/issues/15371#issuecomment-543183849

Comment:
> `cmus` checks for `elogind-devel` for MPRIS support.
> 
> Adding `elogind` to list of cmus's dependency may enrage a lot of people.

So why make elogind a default build option? Do we have some policy on dealing with optional package dependencies?

It's not easy to keep a balance, as every possible additional dependency may be required by someones use-case, and in the end we'll end up with totally bloated void installations. I suppose this needs to be discussed (if it wasn't already), potentially in the mailing list?

There should perhaps be a way to evaluate more properly every new build option that brings in additional runtime dependencies, and consider maybe opting to not making most of those being on by default.

Another approach could be to keep adding them on demand (only if one requests for enabling one's specific use-case), although this will eventually converge to switching on everything.

Yet another (not mutually exclusive), would be to provide a current-minimal repo that builds every package with all build options disabled.

What do you think?