From: Luciogi <Luciogi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] gpgme: package python binding
Date: Sat, 04 Nov 2023 11:08:07 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47057@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]
There is a new pull request by Luciogi against master on the void-packages repository
https://github.com/Luciogi/void-packages gpgme
https://github.com/void-linux/void-packages/pull/47057
gpgme: package python binding
#### 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)
### Desription:
Currently `python3-gpg` exist in void repos, which is not being updating because it fetch src from [PYPI.org](https://pypi.org/project/gpg/). [gpgme](https://www.gnupg.org/) provides python binding in single tarball, so I made new subpackage (gpgme-python3) for `gpgme`.
**gpgme-python3** would replace `python3-gpg`
### reverse deps of `python3-gpg`
- [ ] alot-0.9.1_7
- [ ] caerbannog-0.3_2
- [ ] torbrowser-launcher-0.3.6_2
## Help !!
- What are changes required for `python3-gpg`'s template?
A patch file from https://github.com/void-linux/void-packages/pull/47057.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-gpgme-47057.patch --]
[-- Type: text/x-diff, Size: 1424 bytes --]
From 7af81aa84d600774973c6326b98897a104e9e2c6 Mon Sep 17 00:00:00 2001
From: Luciogi <lucigithubcommit@skiff.com>
Date: Sat, 4 Nov 2023 14:55:50 +0500
Subject: [PATCH] gpgme: package python binding
---
srcpkgs/gpgme/template | 17 +++++++++++++----
1 file changed, 13 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/gpgme/template b/srcpkgs/gpgme/template
index e5db1704b5b98..766c68edb2adf 100644
--- a/srcpkgs/gpgme/template
+++ b/srcpkgs/gpgme/template
@@ -1,13 +1,14 @@
# Template file for 'gpgme'
pkgname=gpgme
version=1.23.1
-revision=1
+revision=2
build_style=gnu-configure
configure_args="--enable-fd-passing
--with-libgpg-error-prefix=$XBPS_CROSS_BASE/usr
- --with-libassuan-prefix=$XBPS_CROSS_BASE/usr"
-hostmakedepends="gnupg pkg-config qt5-host-tools qt5-qmake"
-makedepends="libassuan-devel qt5-tools-devel"
+ --with-libassuan-prefix=$XBPS_CROSS_BASE/usr
+ --enable-languages="python,qt,cpp""
+hostmakedepends="gnupg pkg-config qt5-host-tools qt5-qmake python3-setuptools swig"
+makedepends="libassuan-devel qt5-tools-devel python3-devel"
short_desc="GnuPG Made Easy"
maintainer="Orphaned <orphan@voidlinux.org>"
license="GPL-2.0-or-later, LGPL-2.1-or-later"
@@ -81,3 +82,11 @@ gpgmeqt-devel_package() {
vmove usr/lib/cmake/QGpgme
}
}
+
+gpgme-python3_package() {
+ short_desc+=" - Python binding"
+ depends="gpgme"
+ pkg_install() {
+ vmove "usr/lib/python*"
+ }
+}
next reply other threads:[~2023-11-04 10:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 10:08 Luciogi [this message]
2023-11-04 10:25 ` [PR PATCH] [Updated] gpgme: package python binding [Help] Luciogi
2023-11-04 13:13 ` Luciogi
2023-11-04 13:29 ` Luciogi
2023-11-04 15:32 ` Luciogi
2023-11-04 15:37 ` Luciogi
2023-11-04 19:04 ` Luciogi
2023-11-04 19:16 ` [PR PATCH] [Updated] gpgme: package python binding Luciogi
2023-11-04 19:20 ` [PR REVIEW] " classabbyamp
2023-11-04 20:09 ` [PR PATCH] [Updated] " Luciogi
2023-11-04 20:12 ` Luciogi
2023-11-04 20:13 ` Luciogi
2023-11-04 20:14 ` [PR REVIEW] " Luciogi
2023-11-05 3:29 ` ahesford
2023-11-05 7:56 ` [PR PATCH] [Updated] " Luciogi
2023-11-05 8:33 ` [PR REVIEW] " Luciogi
2023-11-05 12:40 ` classabbyamp
2023-11-05 12:40 ` classabbyamp
2023-11-06 9:37 ` [PR PATCH] [Updated] " Luciogi
2024-02-05 1:45 ` github-actions
2024-02-06 19:01 ` [PR REVIEW] " classabbyamp
2024-02-07 7:55 ` [PR PATCH] [Updated] " Luciogi
2024-02-07 7:55 ` [PR REVIEW] " Luciogi
2024-02-10 8:18 ` [PR PATCH] [Merged]: " classabbyamp
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-47057@inbox.vuxu.org \
--to=luciogi@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).