From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] kgpg: fix
Date: Thu, 26 Sep 2019 18:09:02 +0200 [thread overview]
Message-ID: <20190926160902.yYMsxIYyYG_U9QqPWTOS0CuHxrF9MsAHrbzSkvip4pA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14741@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 711 bytes --]
There is an updated pull request by k4leg against master on the void-packages repository
https://github.com/k4leg/void-packages patch-4
https://github.com/void-linux/void-packages/pull/14741
kgpg: fix
As we know in Void Linux, there are two packages: gnupg & gnupg2. So, although the first time you launch kgpg, it gives you the opportunity to indicate where it is (gpg), but does not apply your actions, although it also indicates by default the correct path to gpg2.
Why not just add gnupg to the dependency, as it refers to /usr/bin/gpg? Because for some reason he does not want to work with him, he wants gnupg2.
A patch file from https://github.com/void-linux/void-packages/pull/14741.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-patch-4-14741.patch --]
[-- Type: text/x-diff, Size: 1526 bytes --]
From c579bcd64b306abbfa09465f2ab45552bcace338 Mon Sep 17 00:00:00 2001
From: k4leg <39882583+k4leg@users.noreply.github.com>
Date: Sun, 22 Sep 2019 22:58:12 +0300
Subject: [PATCH] kgpg: fix
---
srcpkgs/kgpg/template | 26 ++++++++++++++++++++++++++
1 file changed, 26 insertions(+)
create mode 100644 srcpkgs/kgpg/template
diff --git a/srcpkgs/kgpg/template b/srcpkgs/kgpg/template
new file mode 100644
index 00000000000..b307c8c3720
--- /dev/null
+++ b/srcpkgs/kgpg/template
@@ -0,0 +1,26 @@
+# Template file for 'kgpg'
+pkgname=kgpg
+version=19.08.1
+revision=2
+build_style=cmake
+configure_args="-DBUILD_TESTING=OFF"
+hostmakedepends="extra-cmake-modules"
+makedepends="kwindowsystem-devel kcrash-devel kdbusaddons-devel
+ kiconthemes-devel kjobwidgets-devel kio-devel
+ kservice-devel ktextwidgets-devel kxmlgui-devel
+ kwidgetsaddons-devel knotifications-devel kdoctools-devel
+ akonadi-contacts-devel kcontacts-devel boost-devel"
+short_desc="Simple interface for GnuPG, a powerful encryption utility"
+maintainer="k4leg <d0xi@inbox.ru>"
+license="GPL-2.0-only"
+homepage="https://kde.org/applications/utilities/kgpg/"
+distfiles="${KDE_SITE}/applications/${version}/src/${pkgname}-${version}.tar.xz"
+checksum=441a0bfa58df14bad87f5f446b89113dc20365424f6a87aec30125c9221815c5
+
+if [ "$CROSS_BUILD" ]; then
+ hostmakedepends+=" qt5-qmake kcoreaddons-devel kdoctools kconfig"
+fi
+
+post_extract() {
+ sed -i "s/<default>gpg<\/default>/<default>gpg2<\/default>/g" ${XBPS_BUILDDIR}/${pkgname}-${version}/kgpg.kcfg
+}
next prev parent reply other threads:[~2019-09-26 16:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 16:07 [PR PATCH] " voidlinux-github
2019-09-26 16:09 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-26 16:09 ` voidlinux-github [this message]
2019-09-26 16:29 ` voidlinux-github
2019-09-26 16:29 ` voidlinux-github
2019-09-26 18:03 ` voidlinux-github
2019-09-26 18:35 ` voidlinux-github
2019-09-27 15:14 ` voidlinux-github
2019-09-27 15:15 ` voidlinux-github
2019-09-27 15:26 ` voidlinux-github
2019-09-30 18:21 ` voidlinux-github
2019-10-02 14:13 ` voidlinux-github
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=20190926160902.yYMsxIYyYG_U9QqPWTOS0CuHxrF9MsAHrbzSkvip4pA@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).