From: lay-by <lay-by@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: looking-glass-5.0.1
Date: Wed, 19 Oct 2022 05:50:03 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40031@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
There is a new pull request by lay-by against master on the void-packages repository
https://github.com/lay-by/void-packages looking-glass-client
https://github.com/void-linux/void-packages/pull/40031
New package: looking-glass-5.0.1
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **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/40031.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-looking-glass-client-40031.patch --]
[-- Type: text/x-diff, Size: 1414 bytes --]
From 397e5c7f813cca9e4bd404044809fac85e1081d0 Mon Sep 17 00:00:00 2001
From: lay-by <bean_s@riseup.net>
Date: Tue, 18 Oct 2022 22:25:46 -0500
Subject: [PATCH] added looking-glass
---
srcpkgs/looking-glass/template | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
create mode 100644 srcpkgs/looking-glass/template
diff --git a/srcpkgs/looking-glass/template b/srcpkgs/looking-glass/template
new file mode 100644
index 000000000000..b9ce7f13a66b
--- /dev/null
+++ b/srcpkgs/looking-glass/template
@@ -0,0 +1,16 @@
+# Template file for 'looking-glass'
+pkgname=looking-glass
+version=5.0.1
+revision=1
+archs="x86_64"
+wrksrc="$pkgname-B$version/client"
+build_style=cmake
+configure_args="-DENABLE_BACKTRACE=no"
+makedepends="cmake make gcc libglapi libglib-devel nettle-devel gmp-devel fontconfig-devel spice-devel pkg-config libX11-devel libXfixes-devel libXi-devel libXinerama-devel libXcursor-devel libXpresent-devel libxkbcommon-devel libwaylandpp libwaylandpp-devel wayland-protocols dejavu-fonts-ttf libXScrnSaver-devel MesaLib-devel"
+depends="dejavu-fonts-ttf"
+short_desc="Extremely low latency KVMFR for guests with VGA PCI Passthrough"
+maintainer="lay-by <bean_s@riseup.net>"
+license="GPL-2.0-or-later"
+homepage="https://looking-glass.io/"
+distfiles="$homepage/artifact/B$version/source>$pkgname-B$version.tar.gz"
+checksum=15f0c35b195242d6b8087785f76d425e0dffd49ba9d57e26cc26f458973e92cd
next reply other threads:[~2022-10-19 3:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 3:50 lay-by [this message]
2022-10-19 4:48 ` [PR REVIEW] " classabbyamp
2022-10-19 4:48 ` classabbyamp
2022-10-19 4:48 ` classabbyamp
2022-10-19 5:14 ` [PR PATCH] [Updated] " lay-by
2022-10-19 5:18 ` [PR REVIEW] " lay-by
2023-01-18 2:00 ` github-actions
2023-01-20 22:48 ` [PR REVIEW] " JamiKettunen
2023-01-20 22:48 ` JamiKettunen
2023-01-20 22:48 ` JamiKettunen
2023-01-20 22:48 ` JamiKettunen
2023-01-21 2:11 ` JamiKettunen
2023-01-21 2:12 ` JamiKettunen
2023-04-22 1:53 ` github-actions
2023-05-07 1:56 ` [PR PATCH] [Closed]: " github-actions
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-40031@inbox.vuxu.org \
--to=lay-by@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).