From: rien <rien@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: ncspot-0.1.4
Date: Mon, 06 Jul 2020 14:21:48 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23415@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 633 bytes --]
There is a new pull request by rien against master on the void-packages repository
https://github.com/rien/void-packages new/ncspot-0.1.4
https://github.com/void-linux/void-packages/pull/23415
New package: ncspot-0.1.4
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`?
A patch file from https://github.com/void-linux/void-packages/pull/23415.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-new/ncspot-0.1.4-23415.patch --]
[-- Type: text/x-diff, Size: 1145 bytes --]
From 3e64cc2c710f960fff68b7f424cfd9d31a421b31 Mon Sep 17 00:00:00 2001
From: Rien Maertens <rien.maertens@posteo.be>
Date: Mon, 6 Jul 2020 14:08:31 +0200
Subject: [PATCH] New package: ncspot-0.1.4
---
srcpkgs/ncspot/template | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
create mode 100644 srcpkgs/ncspot/template
diff --git a/srcpkgs/ncspot/template b/srcpkgs/ncspot/template
new file mode 100644
index 00000000000..d3f48c9d0a2
--- /dev/null
+++ b/srcpkgs/ncspot/template
@@ -0,0 +1,18 @@
+# Template file for 'ncspot'
+pkgname=ncspot
+version=0.1.4
+revision=1
+build_style=cargo
+hostmakedepends="pkg-config python3"
+makedepends="pulseaudio-devel dbus-devel libressl-devel ncurses-devel"
+depends="pulseaudio dbus libxcb libssl48 ncurses"
+short_desc="Cross-platform ncurses Spotify client written in Rust."
+maintainer="Rien Maertens <rien.maertens@posteo.be>"
+license="BSD-2-Clause"
+homepage="https://github.com/hrkfdn/ncspot/"
+distfiles="https://github.com/hrkfdn/${pkgname}/archive/${version}.tar.gz"
+checksum=bcc4026f51fe4be7351b6e6cd124a5fd4b3af8b6a58f23a0599ce5f34fc4416e
+
+post_install() {
+ vlicense LICENSE
+}
next reply other threads:[~2020-07-06 12:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 12:21 rien [this message]
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 ` [PR PATCH] [Closed]: " rien
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23415@inbox.vuxu.org \
--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).