From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: Cmus doesn't respond to playerctl commands
Date: Thu, 17 Oct 2019 15:49:50 +0200 [thread overview]
Message-ID: <20191017134950.a2NwRaJBLNloi0q61tZtBBAsjHxxrTigTmPOLdZFqI8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15371@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]
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?
next prev parent reply other threads:[~2019-10-17 13:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 20:37 [ISSUE] " voidlinux-github
2019-10-16 1:03 ` voidlinux-github
2019-10-16 9:25 ` voidlinux-github
2019-10-17 11:04 ` [ISSUE] [CLOSED] " voidlinux-github
2019-10-17 13:49 ` voidlinux-github [this message]
2019-10-18 2:45 ` voidlinux-github
2019-10-18 9:54 ` voidlinux-github
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191017134950.a2NwRaJBLNloi0q61tZtBBAsjHxxrTigTmPOLdZFqI8@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).