From: ndowens <ndowens@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] p11-kit: update to 0.23.21
Date: Wed, 11 Nov 2020 21:45:29 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26302@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 311 bytes --]
There is a new pull request by ndowens against master on the void-packages repository
https://github.com/ndowens/void-packages p11-kit
https://github.com/void-linux/void-packages/pull/26302
p11-kit: update to 0.23.21
A patch file from https://github.com/void-linux/void-packages/pull/26302.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-p11-kit-26302.patch --]
[-- Type: text/x-diff, Size: 1655 bytes --]
From 306510e6c040cb6071ad9b1bd86b82366bffb16e Mon Sep 17 00:00:00 2001
From: Nathan Owens <ndowens@artixlinux.org>
Date: Wed, 11 Nov 2020 14:44:45 -0600
Subject: [PATCH] p11-kit: update to 0.23.21
---
srcpkgs/p11-kit/template | 15 ++++++++++-----
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/p11-kit/template b/srcpkgs/p11-kit/template
index e886816f488..290c4620a03 100644
--- a/srcpkgs/p11-kit/template
+++ b/srcpkgs/p11-kit/template
@@ -1,25 +1,30 @@
# Template file for 'p11-kit'
pkgname=p11-kit
-version=0.23.20
+version=0.23.21
revision=1
build_style=gnu-configure
configure_args="--with-module-path=/usr/lib/pkcs11"
-hostmakedepends="automake libtool pkg-config gettext-devel"
-makedepends="libtasn1-devel libffi-devel"
+hostmakedepends="automake libtool pkg-config"
+makedepends="gettext-devel libtasn1-devel libffi-devel"
short_desc="Provides a way to load and enumerate PKCS#11 modules"
maintainer="Orphaned <orphan@voidlinux.org>"
license="BSD-3-Clause"
homepage="https://github.com/p11-glue/p11-kit"
distfiles="${homepage}/releases/download/${version}/p11-kit-${version}.tar.xz"
-checksum=14d86024c3dfd6b967d9bc0b4ec7b2973014fe7423481f4d230a1a63b8aa6104
+checksum=f1baa493f05ca0d867f06bcb54cbb5cdb28c756db07207b6e18de18a87b10627
conf_files="/etc/pkcs11/pkcs11.conf"
+if [ "$CROSS_BUILD" ]; then
+ hostmakedepends+=" gettext-devel"
+fi
+
pre_configure() {
NOCONFIGURE=1 autoreconf -fi
}
post_install() {
- mv ${DESTDIR}/etc/pkcs11/pkcs11.conf.example ${DESTDIR}/etc/pkcs11/pkcs11.conf
+ mv ${DESTDIR}/etc/pkcs11/pkcs11.conf.example \
+ ${DESTDIR}/etc/pkcs11/pkcs11.conf
vlicense COPYING
}
next reply other threads:[~2020-11-11 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 20:45 ndowens [this message]
2020-11-14 0:36 ` [PR PATCH] [Closed]: " ndowens
2020-11-14 1:11 ` [PR PATCH] [Updated] " ndowens
2020-11-14 15:03 ` [PR PATCH] [Merged]: " Hoshpak
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-26302@inbox.vuxu.org \
--to=ndowens@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).