From: kruceter <kruceter@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pkcs11-helper: update to 1.29.0
Date: Wed, 01 Feb 2023 20:23:44 +0100 [thread overview]
Message-ID: <20230201192344.gMM55Fvthea3ruE4nse3GGfeQJl4v5gwGswJAZr4-dk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42017@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1656 bytes --]
New comment by kruceter on void-packages repository
https://github.com/void-linux/void-packages/pull/42017#issuecomment-1412593480
Comment:
Upstream ships tarball with pregenerated auto*hell files. Is this approach favorable?
```diff
diff --git a/srcpkgs/pkcs11-helper/template b/srcpkgs/pkcs11-helper/template
index 8b2f5eb3ac..ac8ebe5138 100644
--- a/srcpkgs/pkcs11-helper/template
+++ b/srcpkgs/pkcs11-helper/template
@@ -4,22 +4,19 @@ version=1.29.0
revision=1
build_style=gnu-configure
configure_args="--enable-doc --disable-static $(vopt_enable threading slotevent) $(vopt_enable threading)"
-hostmakedepends="automake libtool pkg-config doxygen"
+hostmakedepends="libtool pkg-config doxygen"
makedepends="openssl-devel"
short_desc="Library to help simplify interacting with PKCS#11 providers"
maintainer="Aloz1 <kno0001@gmail.com>"
license="GPL-2.0-only, BSD-3-Clause"
homepage="https://github.com/OpenSC/pkcs11-helper"
-distfiles="https://github.com/OpenSC/${pkgname}/archive/${pkgname}-${version}.tar.gz"
-checksum=f87c4ce596ccf6211c0de34923e2977c8892bd773ace75d1261a1908979fc9e8
+changelog="https://raw.githubusercontent.com/OpenSC/pkcs11-helper/master/ChangeLog"
+distfiles="https://github.com/OpenSC/pkcs11-helper/releases/download/pkcs11-helper-${version}/pkcs11-helper-${version}.tar.bz2"
+checksum=996846a3c8395e03d8c0515111dc84d82e6e3648d44ba28cb2dbbbca2d4db7d6
build_options="threading"
build_options_default="threading"
desc_option_threading="Enable threading and slotevent support"
-pre_configure() {
- autoreconf -fi
-}
-
post_install() {
vlicense COPYING
vlicense COPYING.GPL
```
next prev parent reply other threads:[~2023-02-01 19:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 16:24 [PR PATCH] " dkwo
2023-02-01 19:22 ` kruceter
2023-02-01 19:23 ` kruceter [this message]
2023-02-01 19:31 ` kruceter
2023-02-01 20:07 ` [PR PATCH] [Updated] " dkwo
2023-02-02 17:51 ` kruceter
2023-02-02 19:45 ` [PR PATCH] [Merged]: " Vaelatern
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=20230201192344.gMM55Fvthea3ruE4nse3GGfeQJl4v5gwGswJAZr4-dk@z \
--to=kruceter@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).