New comment by ailiop-git on void-packages repository

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

Comment:
> Hm, I think `cmus` would be installed on a desktop environment, and its users are more likely to use a hotkey to interact with cmus (when working with other applications). I think support `playerctl` is a sensible default options.

This is a good example of a conflicting defaults expectation that I was pointing out. I do not see how cmus would be associated with any desktop environment, being a purely terminal-oriented cli utility (and there's always the cmus-remote for controlling it over a unix socket with no external deps). So what's sensible for some population of users will be totally incomprehensible for some other population of users.

Thus my question is more generic than just the case cmu, if we have some policy for dealing with optional build dependencies in general.

> By repo, did you mean binary repository?

Yes I mean an officially published binary repo that builds all packages with minimal dependencies. 

Of course anyone can compile locally with their selection of build opts, but I think it's frustrating for both those that prefer minimal packages and those that need all the bells and whistles.