From: dmarto <dmarto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] opensc: revbump, move onepin-opensc-pkcs11.so to opensc-pkcs11
Date: Mon, 14 Nov 2022 15:31:05 +0100 [thread overview]
Message-ID: <20221114143105.ez1K5J4U7gvmMD58NnMj5jqIb4bRXk7RDwfIx5ZY0nY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36846@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
There is an updated pull request by dmarto against master on the void-packages repository
https://github.com/dmarto/void-packages onepin-opensc
https://github.com/void-linux/void-packages/pull/36846
opensc: revbump, move onepin-opensc-pkcs11.so to opensc-pkcs11
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, **x86_64-glibc**
`usr/lib/pkgconfig/opensc-pkcs11.pc` and `usr/lib/onepin-opensc-pkcs11.so` were left in the main `opensc` package.
I never noticed it before as I have the full suit installed, but while making another pkg for a pcsc driver, this caught my eye.
A patch file from https://github.com/void-linux/void-packages/pull/36846.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-onepin-opensc-36846.patch --]
[-- Type: text/x-diff, Size: 842 bytes --]
From 9e36fa6df0049b6936abb6bd4a077c23434f99ca Mon Sep 17 00:00:00 2001
From: Martin Dimov <martin@dmarto.com>
Date: Mon, 25 Apr 2022 06:16:27 +0300
Subject: [PATCH] opensc: revbump, move onepin-opensc-pkcs11.so to
opensc-pkcs11
---
srcpkgs/opensc/template | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/opensc/template b/srcpkgs/opensc/template
index cadccca0839e..39c56650881e 100644
--- a/srcpkgs/opensc/template
+++ b/srcpkgs/opensc/template
@@ -28,9 +28,12 @@ post_install() {
opensc-pkcs11_package() {
short_desc+=" - pkcs11 library"
pkg_install() {
- vmove usr/lib/pkcs11
- vmove "usr/lib/opensc-pkcs11*"
+ vmove usr/lib/onepin-opensc-pkcs11.so
+ vmove usr/lib/opensc-pkcs11.so
vmove usr/lib/pkcs11-spy.so
+ vmove usr/lib/pkcs11
+
+ vmove usr/lib/pkgconfig/opensc-pkcs11.pc
}
}
next prev parent reply other threads:[~2022-11-14 14:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 3:34 [PR PATCH] " dmarto
2022-05-27 2:17 ` [PR PATCH] [Updated] " dmarto
2022-07-17 12:51 ` dmarto
2022-10-16 2:14 ` github-actions
2022-10-16 11:46 ` [PR PATCH] [Updated] " dmarto
2022-10-16 11:50 ` dmarto
2022-11-13 0:15 ` [PR PATCH] [Updated] " dmarto
2022-11-13 0:31 ` dmarto
2022-11-14 14:31 ` dmarto [this message]
2022-12-04 15:03 ` [PR PATCH] [Closed]: " dmarto
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=20221114143105.ez1K5J4U7gvmMD58NnMj5jqIb4bRXk7RDwfIx5ZY0nY@z \
--to=dmarto@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).