Github messages for voidlinux
 help / color / mirror / Atom feed
From: justinesmithies <justinesmithies@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: swayfx-0.3.1
Date: Sat, 10 Jun 2023 13:03:08 +0200	[thread overview]
Message-ID: <20230610110308.n1eaUbenZ9ZGRa62GpsNWr7q0aNoVNHdeLbi6qrfOtg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44256@inbox.vuxu.org>

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

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

https://github.com/justinesmithies/void-packages master
https://github.com/void-linux/void-packages/pull/44256

New package: swayfx-0.3.1
#### 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)

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

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

From 1cd51b7f30c1b20cff7504726aa9c69d89ccfd9f Mon Sep 17 00:00:00 2001
From: JustineSmithies <justine@smithies.me.uk>
Date: Sun, 4 Jun 2023 13:43:00 +0100
Subject: [PATCH] New package: swayfx-0.3.1

---
 srcpkgs/swayfx/INSTALL           |  5 +++++
 srcpkgs/swayfx/patches/7326.diff | 26 ++++++++++++++++++++++++++
 srcpkgs/swayfx/template          | 23 +++++++++++++++++++++++
 3 files changed, 54 insertions(+)
 create mode 100644 srcpkgs/swayfx/INSTALL
 create mode 100644 srcpkgs/swayfx/patches/7326.diff
 create mode 100644 srcpkgs/swayfx/template

diff --git a/srcpkgs/swayfx/INSTALL b/srcpkgs/swayfx/INSTALL
new file mode 100644
index 000000000000..0120d14908bc
--- /dev/null
+++ b/srcpkgs/swayfx/INSTALL
@@ -0,0 +1,5 @@
+case "${ACTION}" in
+post)
+	setcap CAP_SYS_NICE=+ep usr/bin/sway
+	;;
+esac
diff --git a/srcpkgs/swayfx/patches/7326.diff b/srcpkgs/swayfx/patches/7326.diff
new file mode 100644
index 000000000000..c310f9af4c7c
--- /dev/null
+++ b/srcpkgs/swayfx/patches/7326.diff
@@ -0,0 +1,26 @@
+diff --git a/sway/config.c b/sway/config.c
+index 1f2bb68604..f5efa98a8e 100644
+--- a/sway/config.c
++++ b/sway/config.c
+@@ -37,7 +37,7 @@ struct sway_config *config = NULL;
+
+ static struct xkb_state *keysym_translation_state_create(
+ 		struct xkb_rule_names rules) {
+-	struct xkb_context *context = xkb_context_new(XKB_CONTEXT_NO_FLAGS);
++	struct xkb_context *context = xkb_context_new(XKB_CONTEXT_NO_SECURE_GETENV);
+ 	struct xkb_keymap *xkb_keymap = xkb_keymap_new_from_names(
+ 		context,
+ 		&rules,
+diff --git a/sway/input/keyboard.c b/sway/input/keyboard.c
+index 3f4a7289b9..45a588ecbf 100644
+--- a/sway/input/keyboard.c
++++ b/sway/input/keyboard.c
+@@ -754,7 +754,7 @@ static void handle_xkb_context_log(struct xkb_context *context,
+
+ struct xkb_keymap *sway_keyboard_compile_keymap(struct input_config *ic,
+ 		char **error) {
+-	struct xkb_context *context = xkb_context_new(XKB_CONTEXT_NO_FLAGS);
++	struct xkb_context *context = xkb_context_new(XKB_CONTEXT_NO_SECURE_GETENV);
+ 	if (!sway_assert(context, "cannot create XKB context")) {
+ 		return NULL;
+ 	}
diff --git a/srcpkgs/swayfx/template b/srcpkgs/swayfx/template
new file mode 100644
index 000000000000..ade584f1ddaa
--- /dev/null
+++ b/srcpkgs/swayfx/template
@@ -0,0 +1,23 @@
+# Template file for 'swayfx'
+pkgname=swayfx
+version=0.3.1
+revision=1
+build_style=meson
+configure_args="-Dwerror=false -Db_ndebug=false"
+conf_files="/etc/sway/config"
+hostmakedepends="pkg-config wayland-devel scdoc"
+makedepends="wlroots-devel pcre2-devel json-c-devel pango-devel cairo-devel
+ gdk-pixbuf-devel libevdev-devel"
+depends="libcap-progs swaybg xorg-server-xwayland libxkbcommon>=1.5.0_1"
+short_desc="Sway, but with eye candy"
+maintainer="Justine Smithies <justine@smithies.me.uk>"
+license="MIT"
+homepage="https://github.com/WillPower3309/swayfx"
+changelog="https://github.com/WillPower3309/swayfx/releases"
+distfiles="https://github.com/WillPower3309/swayfx/archive/refs/tags/${version}.tar.gz"
+checksum=42738d9d180d3e481575451612cdbab3bb62df9523c9dea864f267a20801006b
+conflicts="sway"
+
+post_install() {
+	vlicense LICENSE
+}

  parent reply	other threads:[~2023-06-10 11:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-04 12:45 [PR PATCH] " justinesmithies
2023-06-04 12:50 ` paper42
2023-06-07 18:16 ` [PR PATCH] [Updated] " justinesmithies
2023-06-08 18:59 ` justinesmithies
2023-06-08 18:59 ` justinesmithies
2023-06-09  6:51 ` justinesmithies
2023-06-09 17:28 ` justinesmithies
2023-06-09 19:19 ` justinesmithies
2023-06-09 19:19 ` justinesmithies
2023-06-09 20:09 ` justinesmithies
2023-06-10 11:03 ` justinesmithies [this message]
2023-06-10 11:13 ` hervyqa
2023-07-02 22:46 ` hervyqa
2023-07-16 17:45 ` [PR PATCH] [Closed]: " justinesmithies
  -- strict thread matches above, loose matches on Subject: below --
2023-06-03 14:39 [PR PATCH] New package: swayfx justinesmithies
2023-06-04 11:32 ` [PR PATCH] [Updated] New package: swayfx-0.3.1 justinesmithies

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=20230610110308.n1eaUbenZ9ZGRa62GpsNWr7q0aNoVNHdeLbi6qrfOtg@z \
    --to=justinesmithies@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).