From: st3r4g <st3r4g@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] libglvnd: remove excess devel deps, grep license
Date: Sat, 16 May 2020 14:42:20 +0200 [thread overview]
Message-ID: <20200516124220.fqXjNlIeBTQsK93B0-xSNVxiMFGQeSxd_lhojobe2cg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22008@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 387 bytes --]
There is an updated pull request by st3r4g against master on the void-packages repository
https://github.com/st3r4g/void-packages libglvnd-remove-devel-deps
https://github.com/void-linux/void-packages/pull/22008
libglvnd: remove excess devel deps, grep license
Tested building `glu` and `mesa`
A patch file from https://github.com/void-linux/void-packages/pull/22008.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libglvnd-remove-devel-deps-22008.patch --]
[-- Type: text/x-diff, Size: 1189 bytes --]
From fbf081991306481851e2ca83b44b036c6a375300 Mon Sep 17 00:00:00 2001
From: Stefano Ragni <st3r4g@protonmail.com>
Date: Sat, 16 May 2020 10:56:27 +0200
Subject: [PATCH] libglvnd: remove excess devel deps, grep license
---
srcpkgs/libglvnd/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/libglvnd/template b/srcpkgs/libglvnd/template
index b12cb41e6d5..08be3a8ffa7 100644
--- a/srcpkgs/libglvnd/template
+++ b/srcpkgs/libglvnd/template
@@ -1,7 +1,7 @@
# Template file for 'libglvnd'
pkgname=libglvnd
version=1.3.1
-revision=1
+revision=2
wrksrc="libglvnd-v${version}"
build_style=meson
hostmakedepends="pkg-config"
@@ -27,12 +27,12 @@ case "$XBPS_TARGET_MACHINE" in
esac
post_install() {
- $XBPS_FETCH_CMD "https://git.archlinux.org/svntogit/packages.git/plain/trunk/LICENSE?h=packages/libglvnd>LICENSE"
+ grep -A 25 "Copyright (c) 2013, NVIDIA CORPORATION." README.md > LICENSE
vlicense LICENSE
}
libglvnd-devel_package() {
- depends="${makedepends} ${sourcepkg}-${version}_${revision}"
+ depends="${sourcepkg}-${version}_${revision}"
conflicts="MesaLib-devel<19.2.5_2"
short_desc+=" - development files"
pkg_install() {
next prev parent reply other threads:[~2020-05-16 12:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 9:15 [PR PATCH] " st3r4g
2020-05-16 10:14 ` Chocimier
2020-05-16 10:33 ` st3r4g
2020-05-16 10:33 ` st3r4g
2020-05-16 10:33 ` st3r4g
2020-05-16 10:41 ` st3r4g
2020-05-16 10:41 ` st3r4g
2020-05-16 11:57 ` st3r4g
2020-05-16 12:23 ` st3r4g
2020-05-16 12:39 ` st3r4g
2020-05-16 12:42 ` st3r4g [this message]
2020-05-16 12:43 ` [PR PATCH] [Updated] " st3r4g
2020-05-16 12:46 ` st3r4g
2020-05-16 12:47 ` st3r4g
2020-10-01 13:15 ` [PR PATCH] [Closed]: " st3r4g
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=20200516124220.fqXjNlIeBTQsK93B0-xSNVxiMFGQeSxd_lhojobe2cg@z \
--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).