From: Radfordhound <Radfordhound@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] glm: fix license, copy cmake config files
Date: Thu, 22 Dec 2022 02:13:59 +0100 [thread overview]
Message-ID: <20221222011359.G6W8ZzJq-DcES4WVLBZJu1baJkdAb8dJStyPz2avGp4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36213@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 508 bytes --]
There is an updated pull request by Radfordhound against master on the void-packages repository
https://github.com/Radfordhound/void-packages master
https://github.com/void-linux/void-packages/pull/36213
glm: fix license, copy cmake config files
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
A patch file from https://github.com/void-linux/void-packages/pull/36213.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-36213.patch --]
[-- Type: text/x-diff, Size: 1195 bytes --]
From e374415a275593c3cac9518a6a69bc8c07916aa7 Mon Sep 17 00:00:00 2001
From: Graham Scott <Grahamlrscott@gmail.com>
Date: Wed, 21 Dec 2022 19:07:24 -0600
Subject: [PATCH] glm: fix license, copy cmake config files
---
srcpkgs/glm/template | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/glm/template b/srcpkgs/glm/template
index 7ccca2b74ebf..1d9009eb1f2d 100644
--- a/srcpkgs/glm/template
+++ b/srcpkgs/glm/template
@@ -1,7 +1,7 @@
# Template file for 'glm'
pkgname=glm
version=0.9.9.8
-revision=1
+revision=2
build_style=cmake
hostmakedepends="dos2unix unzip"
short_desc="C++ mathematics library for graphics programming"
@@ -19,6 +19,8 @@ do_install() {
for i in glm ; do
vcopy $i usr/include
done
+ vmkdir usr/lib/cmake
+ vcopy cmake/glm usr/lib/cmake
vmkdir usr/share/pkgconfig
vinstall ${FILESDIR}/glm.pc 644 usr/share/pkgconfig
}
@@ -28,7 +30,6 @@ post_install() {
for f in $(find ${DESTDIR}/usr/include -type f); do
dos2unix "$f"
done
- rm -f "${DESTDIR}/usr/include/CMakeLists.txt"
- sed -n '88,110p' manual.md > LICENSE
- vlicense LICENSE
+ rm "${DESTDIR}/usr/include/glm/CMakeLists.txt"
+ vlicense copying.txt LICENSE
}
next prev parent reply other threads:[~2022-12-22 1:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 20:02 [PR PATCH] " Radfordhound
2022-03-18 20:51 ` [PR REVIEW] " tibequadorian
2022-03-18 21:00 ` [PR PATCH] [Updated] " Radfordhound
2022-03-18 21:03 ` [PR REVIEW] " Radfordhound
2022-03-18 22:20 ` [PR PATCH] [Updated] " Radfordhound
2022-03-18 22:20 ` leahneukirchen
2022-03-18 22:25 ` Radfordhound
2022-03-19 0:20 ` [PR REVIEW] " tibequadorian
2022-03-19 0:21 ` tibequadorian
2022-03-19 1:13 ` [PR PATCH] [Updated] " Radfordhound
2022-03-19 1:17 ` [PR REVIEW] " Radfordhound
2022-03-19 1:18 ` Radfordhound
2022-06-29 2:15 ` github-actions
2022-06-29 2:30 ` Radfordhound
2022-09-29 2:14 ` github-actions
2022-10-05 1:13 ` Radfordhound
2022-12-19 4:38 ` [PR REVIEW] " classabbyamp
2022-12-22 0:53 ` [PR PATCH] [Updated] " Radfordhound
2022-12-22 1:13 ` Radfordhound [this message]
2022-12-22 1:16 ` Radfordhound
2023-02-10 18:18 ` [PR PATCH] [Closed]: " classabbyamp
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=20221222011359.G6W8ZzJq-DcES4WVLBZJu1baJkdAb8dJStyPz2avGp4@z \
--to=radfordhound@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).