From: skmpz <skmpz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libevdev: update to 1.13.0.
Date: Sun, 20 Nov 2022 13:35:58 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40646@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]
There is a new pull request by skmpz against master on the void-packages repository
https://github.com/skmpz/void-packages libevdev-1.13.0
https://github.com/void-linux/void-packages/pull/40646
libevdev: update to 1.13.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### 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/40646.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libevdev-1.13.0-40646.patch --]
[-- Type: text/x-diff, Size: 1331 bytes --]
From 39a057962f14c47f4100bf17d98c2a6cdb261fa6 Mon Sep 17 00:00:00 2001
From: skmpz <dem.procopiou@gmail.com>
Date: Sun, 20 Nov 2022 16:35:29 +0400
Subject: [PATCH] libevdev: update to 1.13.0.
---
srcpkgs/libevdev/template | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/libevdev/template b/srcpkgs/libevdev/template
index 87070f3a787b..e742895bf87e 100644
--- a/srcpkgs/libevdev/template
+++ b/srcpkgs/libevdev/template
@@ -1,6 +1,6 @@
# Template file for 'libevdev'
pkgname=libevdev
-version=1.12.0
+version=1.13.0
revision=1
build_style=gnu-configure
configure_args="--disable-gcov"
@@ -10,8 +10,8 @@ short_desc="Wrapper library for evdev devices"
maintainer="Orphaned <orphan@voidlinux.org>"
license="MIT"
homepage="https://www.freedesktop.org/wiki/Software/libevdev/"
-distfiles="${FREEDESKTOP_SITE}/${pkgname}/${pkgname}-${version}.tar.xz"
-checksum=2f729e3480695791f9482e8388bd723402b89f0eaf118057bbdea3cecee9b237
+distfiles="${FREEDESKTOP_SITE}/libevdev/libevdev-${version}.tar.xz"
+checksum=9edf2006cc86a5055279647c38ec923d11a821ee4dc2c3033e8d20e8ee237cd9
post_install() {
vlicense COPYING
@@ -28,6 +28,7 @@ libevdev-devel_package() {
vmove usr/share/man/man3
}
}
+
libevdev-tools_package() {
short_desc+=" - tools"
depends="${sourcepkg}-${version}_${revision}"
next reply other threads:[~2022-11-20 12:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 12:35 skmpz [this message]
2022-11-24 2:32 ` classabbyamp
2022-11-24 5:03 ` [PR PATCH] [Updated] " skmpz
2022-11-24 5:07 ` skmpz
2022-11-25 20:14 ` [PR PATCH] [Merged]: " leahneukirchen
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-40646@inbox.vuxu.org \
--to=skmpz@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).