From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libdrm: update to 2.4.100
Date: Sun, 03 Nov 2019 03:10:17 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-16071@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
There is a new pull request by ndowens against master on the void-packages repository
https://github.com/ndowens/void-packages libdrm
https://github.com/void-linux/void-packages/pull/16071
libdrm: update to 2.4.100
Built against a few packages that uses it and also ran radeontop fine
A patch file from https://github.com/void-linux/void-packages/pull/16071.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libdrm-16071.patch --]
[-- Type: text/x-diff, Size: 1921 bytes --]
From 20590a6898c65d8f7906bbe789f9968b32ffbb4c Mon Sep 17 00:00:00 2001
From: Nathan Owens <ndowens04@gmail.com>
Date: Sat, 2 Nov 2019 21:03:23 -0500
Subject: [PATCH] libdrm: update to 2.4.100
---
common/shlibs | 14 +++++++-------
srcpkgs/libdrm/template | 4 ++--
2 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/common/shlibs b/common/shlibs
index 388f2a9b3ea..c238c61845a 100644
--- a/common/shlibs
+++ b/common/shlibs
@@ -277,13 +277,13 @@ libxkbfile.so.1 libxkbfile-1.0.5_1
libXpm.so.4 libXpm-3.5.7_1
libXmu.so.6 libXmu-1.0.4_1
libXmuu.so.1 libXmu-1.0.4_1
-libdrm.so.2 libdrm-2.4.6_1
-libdrm_radeon.so.1 libdrm-2.4.6_1
-libdrm_intel.so.1 libdrm-2.4.6_1
-libdrm_nouveau.so.2 libdrm-2.4.34_1
-libdrm_amdgpu.so.1 libdrm-2.4.64_1
-libdrm_freedreno.so.1 libdrm-2.4.97_1
-libkms.so.1 libdrm-2.4.6_1
+libdrm.so.2 libdrm-2.4.100_1
+libdrm_radeon.so.1 libdrm-2.4.100_1
+libdrm_intel.so.1 libdrm-2.4.100_1
+libdrm_nouveau.so.2 libdrm-2.4.100_1
+libdrm_amdgpu.so.1 libdrm-2.4.100_1
+libdrm_freedreno.so.1 libdrm-2.4.100_1
+libkms.so.1 libdrm-2.4.100_1
libXxf86vm.so.1 libXxf86vm-1.0.2_1
libXi.so.6 libXi-1.2.1_1
libdmx.so.1 libdmx-1.0.2_1
diff --git a/srcpkgs/libdrm/template b/srcpkgs/libdrm/template
index 77318b0b4c4..dc2dc3ce0e6 100644
--- a/srcpkgs/libdrm/template
+++ b/srcpkgs/libdrm/template
@@ -1,6 +1,6 @@
# Template file for 'libdrm'
pkgname=libdrm
-version=2.4.99
+version=2.4.100
revision=1
wrksrc="drm-libdrm-${version}"
build_style=meson
@@ -12,7 +12,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
license="MIT"
homepage="https://dri.freedesktop.org/"
distfiles="https://gitlab.freedesktop.org/mesa/drm/-/archive/libdrm-${version}/drm-libdrm-${version}.tar.gz"
-checksum=bb4121e6c0966053fa9fa29c066600a8f80fb71a2baadcce75b3c1f138cff479
+checksum=28d524e0ed8dfb064211e864c29799a1140aed1ff39d53fdecc6c9575a4835a8
post_install() {
sed -n 9,25p < libsync.h > LICENSE
next reply other threads:[~2019-11-03 2:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-03 2:10 voidlinux-github [this message]
2019-11-03 9:43 ` voidlinux-github
2019-11-03 15:36 ` [PR PATCH] [Updated] " voidlinux-github
2019-11-03 15:36 ` voidlinux-github
2019-11-03 15:36 ` voidlinux-github
2019-11-04 18:36 ` [PR PATCH] [Merged]: " voidlinux-github
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-16071@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--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).