From: pr2502 <pr2502@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] poppler: add and enable nss build option
Date: Fri, 15 Jul 2022 17:21:39 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38086@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
There is a new pull request by pr2502 against master on the void-packages repository
https://github.com/pr2502/void-ports poppler-nss-opt
https://github.com/void-linux/void-packages/pull/38086
poppler: add and enable nss build option
Void poppler utils are missing the `pdfsig` utility, after adding nss-devel as a build dependency cmake detects it and builds the utility.
#### Testing the changes
- I tested the changes in this PR: **briefly** ?
I've been running this patch on poppler updated to 22.06 without issues for a few weeks, but void got updated to 22.07 before I made a PR, so here is this patch on its own, I haven't tested it much at all on 22.07.
A patch file from https://github.com/void-linux/void-packages/pull/38086.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-poppler-nss-opt-38086.patch --]
[-- Type: text/x-diff, Size: 1593 bytes --]
From 41b00a19a55376acab40ae6110ce7760f83fdde6 Mon Sep 17 00:00:00 2001
From: max <36980911+pr2502@users.noreply.github.com>
Date: Fri, 15 Jul 2022 16:58:36 +0200
Subject: [PATCH] poppler: add and enable nss build option
---
srcpkgs/poppler/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/poppler/template b/srcpkgs/poppler/template
index 74af1e5d2b63..b746e068d6e2 100644
--- a/srcpkgs/poppler/template
+++ b/srcpkgs/poppler/template
@@ -4,7 +4,7 @@
#
pkgname=poppler
version=22.07.0
-revision=1
+revision=2
_testVersion=920c89f8f43bdfe8966c8e397e7f67f5302e9435
build_style=cmake
build_helper="gir"
@@ -14,7 +14,7 @@ configure_args="-DENABLE_UNSTABLE_API_ABI_HEADERS=ON -DENABLE_CPP=ON
-DTESTDATADIR='${XBPS_BUILDDIR}/test-${_testVersion}'"
hostmakedepends="pkg-config glib-devel"
makedepends="libpng-devel libglib-devel cairo-devel tiff-devel lcms2-devel
-libcurl-devel libopenjpeg2-devel $(vopt_if boost boost-devel)"
+libcurl-devel libopenjpeg2-devel $(vopt_if boost boost-devel) $(vopt_if nss nss-devel)"
short_desc="PDF rendering library"
maintainer="Orphaned <orphan@voidlinux.org>"
license="GPL-2.0-or-later, GPL-3.0-or-later"
@@ -25,8 +25,8 @@ distfiles="${homepage}/${pkgname}-${version}.tar.xz
checksum="420230c5c43782e2151259b3e523e632f4861342aad70e7e20b8773d9eaf3428
ca35f168a18038a2d817ea30d6c7b4ab8294a40a5f5950f3c2a15183ba08c900"
-build_options="gir boost"
-build_options_default="gir boost"
+build_options="gir boost nss"
+build_options_default="gir boost nss"
libpoppler_package() {
depends="poppler-data"
next reply other threads:[~2022-07-15 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 15:21 pr2502 [this message]
2022-07-16 13:32 ` sgn
2022-07-16 14:05 ` [PR PATCH] [Closed]: " sgn
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-38086@inbox.vuxu.org \
--to=pr2502@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).