Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: Cmus doesn't respond to playerctl commands
Date: Fri, 18 Oct 2019 04:45:12 +0200	[thread overview]
Message-ID: <20191018024512.h3H7wKfL5db7NifNCW1A7FD_SehN7WIyMCR4vU3udpM@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: 990 bytes --]

New comment by zdtcd on void-packages repository

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

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

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.

I can't speak for everyone since I'm a `mpd` user,
and I use `mpc` to control it instead.

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

By repo, did you mean binary repository?

To disable all options,

```
grep -hr  '^build_options=' srcpkgs/ \
	| cut -d'"' -f2 \
	| tr ' ' '\n' \
	| sort -u \
	| awk -v ORS=',' 'NF{print "~" $0}'
	| sed 's/^.+$/XBPS_PKG_OPTIONS="\0"' >> etc/conf
```

-- 
Danh


  parent reply	other threads:[~2019-10-18  2:45 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
2019-10-18  2:45 ` voidlinux-github [this message]
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=20191018024512.h3H7wKfL5db7NifNCW1A7FD_SehN7WIyMCR4vU3udpM@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).