From: dashezup <dashezup@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] libxkbcommon: update to 1.0.1.
Date: Sun, 27 Sep 2020 20:19:22 +0200 [thread overview]
Message-ID: <20200927181922.qpzQN3v2PVSdcomchHhgfksxVAS98C7sJU5lBuWDf3k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25134@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 731 bytes --]
There is an updated pull request by dashezup against master on the void-packages repository
https://github.com/dashezup/void-packages libxkbcommon-1.0.1
https://github.com/void-linux/void-packages/pull/25134
libxkbcommon: update to 1.0.1.
btw I saw this and added libxkbregistry.so.0 to shlibs
`=> WARNING: libxkbcommon-1.0.1_1: libxkbregistry.so.0 not found in common/shlibs!`
Are those shlibs usually added when there are new ones are found like this, or add only when it's actually needed?
Should I add `shlib_provides="libxkbcommon.so.0 libxkbregistry.so.0"` and `shlib_provides="libxkbcommon-x11.so.0"` to package template?
A patch file from https://github.com/void-linux/void-packages/pull/25134.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libxkbcommon-1.0.1-25134.patch --]
[-- Type: text/x-diff, Size: 3337 bytes --]
From 70f59020a9ebb401000a7d1bdfa4fd2a40aa6c02 Mon Sep 17 00:00:00 2001
From: Dash Eclipse <dash@ezup.dev>
Date: Sun, 27 Sep 2020 18:18:54 +0000
Subject: [PATCH] libxkbcommon: update to 1.0.1.
---
common/shlibs | 1 +
srcpkgs/libxkbcommon/patches/remove-fuzzing.patch | 10 +++++-----
srcpkgs/libxkbcommon/template | 8 +++++---
3 files changed, 11 insertions(+), 8 deletions(-)
diff --git a/common/shlibs b/common/shlibs
index aae753c73a1..f5ee6203ac1 100644
--- a/common/shlibs
+++ b/common/shlibs
@@ -1220,6 +1220,7 @@ libwayland-cursor.so.0 wayland-1.6.0_1
libtomcrypt.so.1 libtomcrypt-1.18.0_1
libHX.so.28 libHX-3.14_1
libxkbcommon.so.0 libxkbcommon-0.2.0_1
+libxkbregistry.so.0 libxkbcommon-1.0.1_1
libxkbcommon-x11.so.0 libxkbcommon-x11-0.4.2_1
libgee-0.8.so.2 libgee08-0.8.2_1
libnettle.so.8 nettle-3.6_1
diff --git a/srcpkgs/libxkbcommon/patches/remove-fuzzing.patch b/srcpkgs/libxkbcommon/patches/remove-fuzzing.patch
index eddc5ce2b5b..46acb48878e 100644
--- a/srcpkgs/libxkbcommon/patches/remove-fuzzing.patch
+++ b/srcpkgs/libxkbcommon/patches/remove-fuzzing.patch
@@ -4,8 +4,8 @@ Reason: removes creation of fuzzing infrastructure which isn't included in the d
--- meson.build
+++ meson.build
-@@ -382,12 +382,6 @@ if get_option('enable-x11')
- executable('test-x11comp', 'test/x11comp.c', dependencies: x11_test_dep)
+@@ -670,12 +670,6 @@
+ message('valgrind not found, disabling valgrind test setup')
endif
-
@@ -14,6 +14,6 @@ Reason: removes creation of fuzzing infrastructure which isn't included in the d
-executable('fuzz-compose', 'fuzz/compose/target.c', dependencies: test_dep)
-
-
- # Demo programs.
- executable('rmlvo-to-kccgst', 'test/rmlvo-to-kccgst.c', dependencies: test_dep)
- executable('print-compiled-keymap', 'test/print-compiled-keymap.c', dependencies: test_dep)
+ # Benchmarks.
+ libxkbcommon_bench_internal = static_library(
+ 'xkbcommon-bench-internal',
diff --git a/srcpkgs/libxkbcommon/template b/srcpkgs/libxkbcommon/template
index 708056d67f7..6ce96ab92c3 100644
--- a/srcpkgs/libxkbcommon/template
+++ b/srcpkgs/libxkbcommon/template
@@ -1,25 +1,27 @@
# Template file for 'libxkbcommon'
pkgname=libxkbcommon
-version=0.10.0
+version=1.0.1
revision=1
wrksrc="${pkgname}-${pkgname#lib}-${version}"
build_style=meson
configure_args="-Denable-wayland=true -Denable-docs=false -Denable-x11=true"
hostmakedepends="pkg-config bison wayland-protocols wayland-devel"
-makedepends="xkeyboard-config libxcb-devel wayland-devel wayland-protocols"
+makedepends="xkeyboard-config libxcb-devel wayland-devel wayland-protocols libxml2-devel"
depends="xkeyboard-config"
short_desc="Library to handle keyboard descriptions"
maintainer="Orphaned <orphan@voidlinux.org>"
license="MIT"
homepage="https://xkbcommon.org/"
distfiles="https://github.com/xkbcommon/libxkbcommon/archive/xkbcommon-${version}.tar.gz"
-checksum=9b4635cf5d9fc0fb9611ceec1780aafc0944299e9a29ab09c18ec2633923b9c3
+checksum=270e2ad4ce5699f633e49042114cb68a5697fa1ed45b65c1d96a833cfac20954
+shlib_provides="libxkbcommon.so.0 libxkbregistry.so.0"
pkg_install() {
vlicense LICENSE
}
libxkbcommon-x11_package() {
+ shlib_provides="libxkbcommon-x11.so.0"
short_desc+=" - X11 support"
pkg_install() {
vmove "usr/lib/*x11*.so.*"
next prev parent reply other threads:[~2020-09-27 18:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 17:12 [PR PATCH] " dashezup
2020-09-27 18:19 ` dashezup [this message]
2020-09-29 14:08 ` ahesford
2020-09-29 20:59 ` [PR PATCH] [Updated] " dashezup
2020-09-29 21:26 ` dashezup
2020-09-29 21:55 ` dashezup
2020-09-29 21:55 ` dashezup
2020-09-29 21:56 ` [PR PATCH] [Updated] " dashezup
2020-09-29 22:12 ` dashezup
2020-09-29 22:12 ` dashezup
2020-09-29 22:42 ` dashezup
2020-09-30 1:24 ` [PR PATCH] [Updated] " ahesford
2020-09-30 1:29 ` ahesford
2020-09-30 9:48 ` dashezup
2020-09-30 12:39 ` [PR PATCH] [Closed]: " ahesford
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=20200927181922.qpzQN3v2PVSdcomchHhgfksxVAS98C7sJU5lBuWDf3k@z \
--to=dashezup@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).