Github messages for voidlinux
 help / color / mirror / Atom feed
From: oynqr <oynqr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: solo2-cli-0.2.2
Date: Wed, 19 Apr 2023 12:15:57 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43523@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]

There is a new pull request by oynqr against master on the void-packages repository

https://github.com/oynqr/void-packages solo2-cli
https://github.com/void-linux/void-packages/pull/43523

New package: solo2-cli-0.2.2
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->

Companion software for solo v2 security keys. Successfully updated two keys' firmware. Bash and zsh completions work, didn't try fish.

A patch file from https://github.com/void-linux/void-packages/pull/43523.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-solo2-cli-43523.patch --]
[-- Type: text/x-diff, Size: 1810 bytes --]

From 990b5ce36e662e996139a1fb0a49d0083ee315e4 Mon Sep 17 00:00:00 2001
From: Philipp David <pd@3b.pm>
Date: Wed, 19 Apr 2023 12:02:20 +0200
Subject: [PATCH] New package: solo2-cli-0.2.2

---
 srcpkgs/solo2-cli/template | 30 ++++++++++++++++++++++++++++++
 1 file changed, 30 insertions(+)
 create mode 100644 srcpkgs/solo2-cli/template

diff --git a/srcpkgs/solo2-cli/template b/srcpkgs/solo2-cli/template
new file mode 100644
index 000000000000..e61154b73bab
--- /dev/null
+++ b/srcpkgs/solo2-cli/template
@@ -0,0 +1,30 @@
+# Template file for 'solo2-cli'
+pkgname=solo2-cli
+version=0.2.2
+revision=1
+build_style=cargo
+hostmakedepends="pkg-config"
+makedepends="eudev-libudev-devel pcsclite-devel"
+short_desc="CLI tools for SoloKeys Solo 2 security keys"
+maintainer="Philipp David <pd@3b.pm>"
+license="Apache-2.0"
+homepage="https://github.com/solokeys/solo2-cli"
+distfiles="https://github.com/solokeys/solo2-cli/archive/v${version}.tar.gz
+ https://github.com/solokeys/solo2-cli/releases/download/v$version/solo2.completions.bash
+ https://github.com/solokeys/solo2-cli/releases/download/v$version/solo2.completions.fish
+ https://github.com/solokeys/solo2-cli/releases/download/v$version/solo2.completions.zsh"
+checksum="49a30c5ee6f38be968a520089741f8b936099611e98e6bf2b25d05e5e9335fb4
+ 09e5ae1da36e3fbb2e9183188c93277ac113fc2397f3e2447abdf7c718037f0e
+ d002a00bc6a58b23828d2cf7fcc49793dc34185c13aa6858622cda9a28a45379
+ eeda949e2a282cbbc759be939df1e0d96c50578a441dc6caa86a48a7a264a200"
+skip_extraction="solo2.completions.bash
+ solo2.completions.fish
+ solo2.completions.zsh"
+
+post_install() {
+	for shell in bash fish zsh; do
+		vcompletion "$XBPS_SRCDISTDIR/${pkgname}-${version}/solo2.completions.${shell}" \
+			"${shell}" solo2
+	done
+	vinstall 70-solo2.rules 644 usr/lib/udev/rules.d
+}

             reply	other threads:[~2023-04-19 10:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19 10:15 oynqr [this message]
2023-06-24 12:09 ` [PR PATCH] [Merged]: " Duncaen

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-43523@inbox.vuxu.org \
    --to=oynqr@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).