From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: gcr4-4.0.0
Date: Tue, 22 Nov 2022 21:03:03 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40701@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]
There is a new pull request by oreo639 against master on the void-packages repository
https://github.com/oreo639/void-packages gcr4
https://github.com/void-linux/void-packages/pull/40701
New package: gcr4-4.0.0
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **NO**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/40701.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-gcr4-40701.patch --]
[-- Type: text/x-diff, Size: 3154 bytes --]
From 8bed18670d619b7e360eb0eae1e9b53b1072cead Mon Sep 17 00:00:00 2001
From: Michal Vasilek <michal@vasilek.cz>
Date: Tue, 13 Sep 2022 00:03:12 +0200
Subject: [PATCH] New package: gcr4-4.0.0
---
common/shlibs | 2 ++
srcpkgs/gcr4-devel | 1 +
srcpkgs/gcr4/template | 50 +++++++++++++++++++++++++++++++++++++++++++
srcpkgs/gcr4/update | 1 +
4 files changed, 54 insertions(+)
create mode 120000 srcpkgs/gcr4-devel
create mode 100644 srcpkgs/gcr4/template
create mode 100644 srcpkgs/gcr4/update
diff --git a/common/shlibs b/common/shlibs
index 7764c5c6de8b..65652c93c2a0 100644
--- a/common/shlibs
+++ b/common/shlibs
@@ -1036,6 +1036,8 @@ libudisks2.so.0 udisks2-1.93.0_1
libgcr-base-3.so.1 gcr-3.3.92_1
libgck-1.so.0 gcr-3.8.0_1
libgcr-ui-3.so.1 gcr-3.8.0_1
+libgck-2.so.0 gcr4-4.0.0_1
+libgcr-4.so.0 gcr4-4.0.0_1
libcld2.so cld2-0.0.1.20150821_1
libcld2_full.so cld2-full-0.0.1.20150821_1
libwacom.so.2 libwacom-0.3_1
diff --git a/srcpkgs/gcr4-devel b/srcpkgs/gcr4-devel
new file mode 120000
index 000000000000..e85b363d95de
--- /dev/null
+++ b/srcpkgs/gcr4-devel
@@ -0,0 +1 @@
+gcr4
\ No newline at end of file
diff --git a/srcpkgs/gcr4/template b/srcpkgs/gcr4/template
new file mode 100644
index 000000000000..b9bec1d0d8f8
--- /dev/null
+++ b/srcpkgs/gcr4/template
@@ -0,0 +1,50 @@
+# Template file for 'gcr4'
+pkgname=gcr4
+version=4.0.0
+revision=1
+build_style=meson
+build_helper="gir"
+wrksrc="gcr-${version}"
+configure_args="$(vopt_bool gir introspection) $(vopt_bool gir gtk_doc)"
+hostmakedepends="gettext glib-devel gnupg gi-docgen gettext pkg-config openssh
+ libxslt $(vopt_if gir vala)"
+makedepends="libgcrypt-devel libsecret-devel p11-kit-devel libxslt-devel gtk4-devel"
+depends="desktop-file-utils hicolor-icon-theme gnupg"
+checkdepends="dbus"
+short_desc="GNOME crypto package"
+maintainer="Orphaned <orphan@voidlinux.org>"
+license="LGPL-2.0-or-later, LGPL-2.1-or-later, GPL-2.0-or-later"
+homepage="https://gitlab.gnome.org/GNOME/gcr"
+changelog="https://gitlab.gnome.org/GNOME/gcr/-/raw/master/NEWS"
+distfiles="${GNOME_SITE}/gcr/${version%.*}/gcr-${version}.tar.xz"
+checksum=c45855924f0ee7bab43e2dd38bfafd2ac815c6e9864341c0161e171173dcec7c
+make_check_pre="dbus-run-session"
+#make_check=no # Gcr:ERROR:../gcr/test-gnupg-collection.c:203:test_load: assertion failed: (record)
+
+# Package build options
+build_options="gir"
+build_options_default="gir"
+
+post_patch() {
+ vsed -e "s/gcr_soversion = .*/gcr_soversion = '0'/" -i meson.build
+ vsed -e "s/gck_soversion = .*/gck_soversion = '0'/" -i meson.build
+}
+
+post_install() {
+ rm ${DESTDIR}/usr/libexec/gcr-ssh-agent
+}
+
+gcr4-devel_package() {
+ depends="${makedepends} ${sourcepkg}>=${version}_${revision}"
+ short_desc+=" - development files"
+ pkg_install() {
+ vmove usr/include
+ vmove usr/lib/pkgconfig
+ vmove "usr/lib/*.so"
+ if [ "$build_option_gir" ]; then
+ vmove usr/share/gir-1.0
+ vmove usr/share/doc
+ vmove usr/share/vala
+ fi
+ }
+}
diff --git a/srcpkgs/gcr4/update b/srcpkgs/gcr4/update
new file mode 100644
index 000000000000..81e9823e570d
--- /dev/null
+++ b/srcpkgs/gcr4/update
@@ -0,0 +1 @@
+pkgname="gcr"
next reply other threads:[~2022-11-22 20:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 20:03 oreo639 [this message]
2022-11-22 20:17 ` [PR PATCH] [Updated] " oreo639
2022-11-22 20:24 ` [PR REVIEW] " paper42
2022-11-22 20:55 ` [PR PATCH] [Updated] " oreo639
2022-11-22 20:55 ` [PR REVIEW] " oreo639
2022-11-24 23:13 ` JamiKettunen
2022-12-04 13:23 ` paper42
2022-12-04 17:47 ` [PR PATCH] [Updated] " oreo639
2022-12-04 18:02 ` [PR REVIEW] " oreo639
2022-12-11 21:01 ` [PR PATCH] [Merged]: " paper42
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-40701@inbox.vuxu.org \
--to=oreo639@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).