From: rien <rien@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: ncspot-0.2.0
Date: Sun, 17 Apr 2022 20:51:25 +0200 [thread overview]
Message-ID: <20220417185125.wu1nZ3b-4Ehg0GfbGWtQ1_B0iqExgmDNPg5EVE16j7A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23415@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 479 bytes --]
There's a closed pull request on the void-packages repository
New package: ncspot-0.2.0
https://github.com/void-linux/void-packages/pull/23415
Description:
This packages [ncspot](https://github.com/hrkfdn/ncspot), a ncurses Spotify client.
It is currently built with a pulseaudio backend (default), but it can be configured to use alsa or portaudio. Is there a policy preferring an audio backend? Or should I create two (sub)packages: `ncspot-pulseaudio` and `ncspot-alsa`?
next prev parent reply other threads:[~2022-04-17 18:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 12:21 [PR PATCH] New package: ncspot-0.1.4 rien
2020-07-06 12:57 ` rien
2020-07-06 13:00 ` [PR PATCH] [Updated] " rien
2020-07-06 13:00 ` rien
2020-07-06 13:06 ` [PR REVIEW] " ericonr
2020-07-06 13:06 ` ericonr
2020-07-06 13:06 ` ericonr
2020-07-06 13:07 ` ericonr
2020-07-06 13:10 ` rien
2020-07-06 13:16 ` ericonr
2020-07-06 18:33 ` Chocimier
2020-07-06 19:36 ` [PR PATCH] [Updated] " rien
2020-07-06 19:37 ` rien
2020-07-07 8:15 ` rien
2020-07-07 8:23 ` rien
2020-07-07 11:58 ` [PR REVIEW] " rien
2020-07-26 1:48 ` fosslinux
2020-07-27 10:30 ` [PR PATCH] [Updated] " rien
2020-07-27 10:31 ` rien
2020-07-27 11:07 ` New package: ncspot-0.2.0 rien
2020-07-27 13:14 ` [PR PATCH] [Updated] " rien
2020-07-27 13:17 ` rien
2022-04-17 2:06 ` github-actions
2022-04-17 18:51 ` rien [this message]
2020-07-24 20:35 [PR PATCH] New Package: ncs-spot-0.2.0 ThatGeekyWeeb
2020-08-15 11:15 ` [PR PATCH] [Closed]: New Package: ncspot-0.2.0 ThatGeekyWeeb
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=20220417185125.wu1nZ3b-4Ehg0GfbGWtQ1_B0iqExgmDNPg5EVE16j7A@z \
--to=rien@users.noreply.github.com \
--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).