From: st3r4g <st3r4g@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libwacom: update to 1.3, remove some -devel deps
Date: Mon, 11 May 2020 17:53:57 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21840@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 601 bytes --]
There is a new pull request by st3r4g against master on the void-packages repository
https://github.com/st3r4g/void-packages libwacom-1.3
https://github.com/void-linux/void-packages/pull/21840
libwacom: update to 1.3, remove some -devel deps
`libwacom-devel` is pulling in `gtk+-devel` (unnecessarily imo), which has a big dependency tree. So I restricted `depends` to just the stuff listed in Requires.private from the .pc file.
Tested this by building `libinput`.
Pinging the previous updater @pullmoll
A patch file from https://github.com/void-linux/void-packages/pull/21840.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libwacom-1.3-21840.patch --]
[-- Type: text/x-diff, Size: 1337 bytes --]
From 9efb41e2a2ce963845d3e517716a990f34e55db4 Mon Sep 17 00:00:00 2001
From: Stefano Ragni <st3r4g@protonmail.com>
Date: Mon, 11 May 2020 17:03:34 +0200
Subject: [PATCH] libwacom: update to 1.3, remove some -devel deps
---
srcpkgs/libwacom/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/libwacom/template b/srcpkgs/libwacom/template
index 7ab0e9f3fc2..6f9d5563476 100644
--- a/srcpkgs/libwacom/template
+++ b/srcpkgs/libwacom/template
@@ -1,6 +1,6 @@
# Template file for 'libwacom'
pkgname=libwacom
-version=1.2
+version=1.3
revision=1
build_style=meson
build_helper="qemu"
@@ -13,14 +13,14 @@ license="MIT"
homepage="https://github.com/linuxwacom/libwacom"
changelog="https://raw.githubusercontent.com/linuxwacom/libwacom/master/NEWS"
distfiles="https://github.com/linuxwacom/libwacom/releases/download/${pkgname}-${version}/${pkgname}-${version}.tar.bz2"
-checksum=c204cfdee2159d124a4f5ecc8970bbd72f9adf5ad7fd94b66798f93db1f863c3
+checksum=e19ce00fe1e074cc54ffd198dda6c6f1ec389e5c913134adc8795f2c5e63883c
post_install() {
vlicense COPYING
}
libwacom-devel_package() {
- depends="${makedepends} ${sourcepkg}>=${version}_${revision}"
+ depends="libgudev-devel ${sourcepkg}>=${version}_${revision}"
short_desc+=" - development files"
pkg_install() {
vmove usr/include
next reply other threads:[~2020-05-11 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 15:53 st3r4g [this message]
2020-05-11 18:13 ` [PR PATCH] [Merged]: " Hoshpak
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-21840@inbox.vuxu.org \
--to=st3r4g@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).