Github messages for voidlinux
 help / color / mirror / Atom feed
From: RunningDroid <RunningDroid@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: drm_info-2.4.0
Date: Wed, 09 Nov 2022 03:59:20 +0100	[thread overview]
Message-ID: <20221109025920.H7YsNq1HcG-MjPCMDrCWJmuQrf-iQGNlUs19q51RAH8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40378@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1349 bytes --]

There is an updated pull request by RunningDroid against master on the void-packages repository

https://github.com/RunningDroid/void-packages add_drm_info
https://github.com/void-linux/void-packages/pull/40378

New package: drm_info-2.4.0
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

This builds with meson so the checks are going to be broken until python 3.11 is done.

<!--
#### 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/40378.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-add_drm_info-40378.patch --]
[-- Type: text/x-diff, Size: 1138 bytes --]

From 93219b1e72f12e25c150722ffbc534363d1ed249 Mon Sep 17 00:00:00 2001
From: RunningDroid <runningdroid@zoho.com>
Date: Mon, 7 Nov 2022 19:32:44 -0500
Subject: [PATCH] New package: drm_info-2.4.0

---
 srcpkgs/drm_info/template | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)
 create mode 100644 srcpkgs/drm_info/template

diff --git a/srcpkgs/drm_info/template b/srcpkgs/drm_info/template
new file mode 100644
index 000000000000..7fe37abc6ecb
--- /dev/null
+++ b/srcpkgs/drm_info/template
@@ -0,0 +1,18 @@
+# Template file for 'drm_info'
+pkgname=drm_info
+version=2.4.0
+revision=1
+#wrksrc="drm_info-v${version}"
+build_style=meson
+hostmakedepends="pkg-config scdoc"
+makedepends="libdrm-devel json-c-devel"
+short_desc="Small utility to dump info about DRM devices"
+maintainer="RunningDroid <runningdroid@zoho.com>"
+license="MIT"
+homepage="https://gitlab.freedesktop.org/emersion/drm_info"
+distfiles="https://gitlab.freedesktop.org/emersion/drm_info/-/archive/v${version}/drm_info-v${version}.tar.bz2"
+checksum=bbf47df5e07ae36440d6cb24bc9f7da414329154f92c7988da11b10d25ce2687
+
+post_install() {
+	vlicense LICENSE
+}

  reply	other threads:[~2022-11-09  2:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08  1:14 [PR PATCH] " RunningDroid
2022-11-09  2:59 ` RunningDroid [this message]
2022-11-09  4:09 ` [PR PATCH] [Updated] " RunningDroid
2022-11-09  4:39 ` RunningDroid
2022-11-09  4:41 ` RunningDroid
2022-11-25 17:37 ` JamiKettunen
2023-02-24  2:00 ` github-actions
2023-02-24  2:19 ` [PR PATCH] [Updated] " RunningDroid
2023-02-24  3:07 ` RunningDroid
2023-02-24  3:16 ` RunningDroid
2023-05-27  1:52 ` github-actions
2023-05-27 23:34 ` [PR PATCH] [Updated] " RunningDroid
2023-06-23 20:40 ` RunningDroid
2023-06-23 20:43 ` [PR PATCH] [Merged]: " Duncaen

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=20221109025920.H7YsNq1HcG-MjPCMDrCWJmuQrf-iQGNlUs19q51RAH8@z \
    --to=runningdroid@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).