From: user18130814200115-2 <user18130814200115-2@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: lswt
Date: Sun, 09 Jan 2022 21:41:35 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34969@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
There is a new pull request by user18130814200115-2 against master on the void-packages repository
https://github.com/user18130814200115-2/void-packages lswt
https://github.com/void-linux/void-packages/pull/34969
New package: lswt
<!-- 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 [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](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, (aarch64-musl)
A patch file from https://github.com/void-linux/void-packages/pull/34969.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-lswt-34969.patch --]
[-- Type: text/x-diff, Size: 3167 bytes --]
From 28323cd3ce6d71644b070d0aaa20f280d3ef8394 Mon Sep 17 00:00:00 2001
From: user18130814200115-2
<66143190+user18130814200115-2@users.noreply.github.com>
Date: Sun, 9 Jan 2022 20:27:13 +0000
Subject: [PATCH 1/2] Added lswt template
New template for lswt, a program that allows one to list wayland toplevels using the foreign-toplevel-management-unstable-v1 protocol
---
srcpkgs/lswt/template | 13 +++++++++++++
1 file changed, 13 insertions(+)
create mode 100644 srcpkgs/lswt/template
diff --git a/srcpkgs/lswt/template b/srcpkgs/lswt/template
new file mode 100644
index 000000000000..eaf0f46b0704
--- /dev/null
+++ b/srcpkgs/lswt/template
@@ -0,0 +1,13 @@
+# Template file for 'lswt'
+pkgname=lswt
+version=v1.0.2
+revision=1
+build_style=gnu-makefile
+makedepends="wayland-devel"
+short_desc="List wayland toplevels using foreign-toplevel-management-unstable-v1"
+maintainer="Thijs Wester <void@wester.digital>"
+license="GPL-3.0-only"
+homepage="https://git.sr.ht/~leon_plickat/lswt"
+changelog="https://git.sr.ht/~leon_plickat/lswt/refs/${version}"
+distfiles="https://git.sr.ht/~leon_plickat/lswt/archive/${version}.tar.gz"
+checksum="28810c124c0d017ffe41e4b91461a07692aa12a3cd49261c3297dfb0dcf2f4cf"
From 74c952132602fe5a000c99dcd21d4582777cb313 Mon Sep 17 00:00:00 2001
From: user18130814200115-2
<66143190+user18130814200115-2@users.noreply.github.com>
Date: Sun, 9 Jan 2022 20:30:29 +0000
Subject: [PATCH 2/2] lswt: PATCH disable execinfo.h
Only include execinfo.h when GLIBC is used.
This patch is from the upstream repository but is not present in any release yet
---
srcpkgs/lswt/patches/execinfo.patch | 43 +++++++++++++++++++++++++++++
1 file changed, 43 insertions(+)
create mode 100644 srcpkgs/lswt/patches/execinfo.patch
diff --git a/srcpkgs/lswt/patches/execinfo.patch b/srcpkgs/lswt/patches/execinfo.patch
new file mode 100644
index 000000000000..292d6900256d
--- /dev/null
+++ b/srcpkgs/lswt/patches/execinfo.patch
@@ -0,0 +1,43 @@
+From 389b2578b27b1f3dc65952bf0d3f98e12410a8b8 Mon Sep 17 00:00:00 2001
+From: Leon Henrik Plickat <leonhenrik.plickat@stud.uni-goettingen.de>
+Date: Fri, 26 Nov 2021 13:45:06 +0100
+Subject: [PATCH] Only include execinfo.h when GLIBC is used
+
+---
+ lswt.c | 5 +++++
+ 1 file changed, 5 insertions(+)
+
+diff --git a/lswt.c b/lswt.c
+index b61463d..f5fe78a 100644
+--- a/lswt.c
++++ b/lswt.c
+@@ -27,8 +27,11 @@
+ #include <wayland-client.h>
+
+ #ifdef __linux__
++#include <features.h>
++#ifdef __GLIBC__
+ #include<execinfo.h>
+ #endif
++#endif
+
+ #include "xdg-output-unstable-v1.h"
+ #include "wlr-foreign-toplevel-management-unstable-v1.h"
+@@ -642,6 +645,7 @@ static void handle_error (int signum)
+ fputs(msg, stderr);
+
+ #ifdef __linux__
++#ifdef __GLIBC__
+ fputs("Attempting to get backtrace:\n", stderr);
+
+ /* In some rare cases, getting a backtrace can also cause a segfault.
+@@ -652,6 +656,7 @@ static void handle_error (int signum)
+ const int calls = backtrace(buffer, sizeof(buffer) / sizeof(void *));
+ backtrace_symbols_fd(buffer, calls, fileno(stderr));
+ fputs("\n", stderr);
++#endif
+ #endif
+
+ /* Let the default handlers deal with the rest. */
+--
+2.32.0
next reply other threads:[~2022-01-09 20:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 20:41 user18130814200115-2 [this message]
2022-01-10 18:58 ` [PR PATCH] [Updated] " user18130814200115-2
2022-01-10 19:22 ` user18130814200115-2
2022-01-12 19:54 ` [PR REVIEW] " ifreund
2022-01-12 21:48 ` [PR PATCH] [Updated] " user18130814200115-2
2022-01-12 21:48 ` [PR REVIEW] " user18130814200115-2
2022-01-12 21:49 ` user18130814200115-2
2022-01-13 9:30 ` [PR PATCH] [Updated] " user18130814200115-2
2022-04-14 2:08 ` New package: lswt-v1.0.2 github-actions
2022-06-21 2:13 ` [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-34969@inbox.vuxu.org \
--to=user18130814200115-2@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).