Github messages for voidlinux
 help / color / mirror / Atom feed
From: Calandracas606 <Calandracas606@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] libpciaccess: update to 0.17.
Date: Fri, 26 Jan 2024 15:42:35 +0100	[thread overview]
Message-ID: <20240126144235.9AD4024A18@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48037@inbox.vuxu.org>

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

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

https://github.com/Calandracas606/void-packages libpciaccess0.16
https://github.com/void-linux/void-packages/pull/48037

libpciaccess: update to 0.17.
<!-- Uncomment relevant sections and delete options which are not applicable -->

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

<!--
#### 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, x86_64-glibc
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - x86_64-musl
  - i686
  - aarch64-musl (cross)
  - armv7l (cross)
  - armv6l-musl (cross)



A patch file from https://github.com/void-linux/void-packages/pull/48037.patch is attached

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

From 98da336348888e73f51b840d0b6bab9a02b4dfff Mon Sep 17 00:00:00 2001
From: Daniel Martinez <danielmartinez@cock.li>
Date: Tue, 2 Jan 2024 20:55:10 -0500
Subject: [PATCH] libpciaccess: update to 0.17.

---
 srcpkgs/libpciaccess/template | 17 +++++++++--------
 1 file changed, 9 insertions(+), 8 deletions(-)

diff --git a/srcpkgs/libpciaccess/template b/srcpkgs/libpciaccess/template
index 9aaf0a3291aba..ed228e0196198 100644
--- a/srcpkgs/libpciaccess/template
+++ b/srcpkgs/libpciaccess/template
@@ -1,14 +1,16 @@
-# Template build file for 'libpciaccess'.
+# Template file for 'libpciaccess'
 pkgname=libpciaccess
-version=0.16
+version=0.17
 revision=1
-build_style=gnu-configure
-short_desc="X11 PCI Access library"
+build_style=meson
+hostmakedepends="pkg-config"
+makedepends="zlib-devel"
+short_desc="Generic PCI access library"
 maintainer="Orphaned <orphan@voidlinux.org>"
 license="MIT"
-homepage="http://xorg.freedesktop.org/"
-distfiles="${XORG_SITE}/lib/$pkgname-$version.tar.bz2"
-checksum=214c9d0d884fdd7375ec8da8dcb91a8d3169f263294c9a90c575bf1938b9f489
+homepage="https://gitlab.freedesktop.org/xorg/lib/libpciaccess"
+distfiles="https://gitlab.freedesktop.org/xorg/lib/libpciaccess/-/archive/libpciaccess-${version}/libpciaccess-libpciaccess-${version}.tar.gz"
+checksum=951c7556b9222b755a8f2d0bc6cc9370529b78df461000103d7cea839c13db72
 
 post_install() {
 	vlicense COPYING
@@ -20,7 +22,6 @@ libpciaccess-devel_package() {
 	pkg_install() {
 		vmove usr/include
 		vmove usr/lib/pkgconfig
-		vmove "usr/lib/*.a"
 		vmove "usr/lib/*.so"
 	}
 }

  reply	other threads:[~2024-01-26 14:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03  1:59 [PR PATCH] " Calandracas606
2024-01-26 14:42 ` Calandracas606 [this message]
2024-02-13 16:39 ` [PR PATCH] [Closed]: " Calandracas606
2024-02-13 16:39 ` Calandracas606

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=20240126144235.9AD4024A18@inbox.vuxu.org \
    --to=calandracas606@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).