Github messages for voidlinux
 help / color / mirror / Atom feed
From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] update river and waylock
Date: Fri, 31 Mar 2023 20:37:50 +0200	[thread overview]
Message-ID: <20230331183750.AvtT0pss9oXldobZbkw8HLJe_n_KuYfV-XfTqSQFPSI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43143@inbox.vuxu.org>

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

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

https://github.com/dkwo/void-packages river
https://github.com/void-linux/void-packages/pull/43143

update river and waylock
- I tested the changes in this PR: yes. been running them for months, built with zig-static
- I built this PR locally for my native architecture, (x86_64-musl)

cc maintainer @ifreund 

[ci skip]

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

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

From c2c6b3b71cd58860452498c1e7b8a89e194470f9 Mon Sep 17 00:00:00 2001
From: dkwo <nicolopiazzalunga@gmail.com>
Date: Wed, 28 Dec 2022 18:11:24 +0100
Subject: [PATCH 1/2] river: update to 0.2.4

---
 srcpkgs/river/template | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/srcpkgs/river/template b/srcpkgs/river/template
index 431aa4bd8e8e..f49850646291 100644
--- a/srcpkgs/river/template
+++ b/srcpkgs/river/template
@@ -1,21 +1,21 @@
 # Template file for 'river'
 pkgname=river
-version=0.2.3
+version=0.2.4
 revision=1
 build_style=zig-build
-configure_args="$(vopt_if xwayland -Dxwayland) -Dpie"
+configure_args="$(vopt_if xwayland -Dxwayland) -Dpie -Dstrip"
 hostmakedepends="pkg-config wayland-devel scdoc"
-makedepends="wlroots-devel libevdev-devel"
+makedepends="wlroots-devel libevdev-devel pixman-devel
+ wayland-protocols libxkbcommon-devel wayland-devel"
 depends="$(vopt_if xwayland xorg-server-xwayland)"
 short_desc="Dynamic tiling Wayland compositor"
 maintainer="Isaac Freund <mail@isaacfreund.com>"
 license="GPL-3.0-or-later"
 homepage="https://github.com/riverwm/river"
-distfiles="${homepage}/releases/download/v${version}/river-${version}.tar.gz"
-checksum=7acdd2b929e16a20006b4baf1f29e7a8dc7f70cf5747e1503a610a90d1637132
+distfiles="https://github.com/riverwm/river/releases/download/v${version}/river-${version}.tar.gz"
+checksum=26c1c41a65ce3804069afad6988410515cf478d2b76303ebc699766d3d4dc69f
 
 build_options="xwayland"
-build_options_default="xwayland"
 desc_option_xwayland="Enable Xwayland support"
 
 post_install() {

From 291f1420c4c6dbb3980616d4323d1c19a0f7fcef Mon Sep 17 00:00:00 2001
From: dkwo <nicolopiazzalunga@gmail.com>
Date: Sun, 1 Jan 2023 13:22:41 +0100
Subject: [PATCH 2/2] waylock: update to 0.6.2

---
 srcpkgs/waylock/template | 15 ++++++++-------
 1 file changed, 8 insertions(+), 7 deletions(-)

diff --git a/srcpkgs/waylock/template b/srcpkgs/waylock/template
index 75878edae943..f8c8624b844a 100644
--- a/srcpkgs/waylock/template
+++ b/srcpkgs/waylock/template
@@ -1,16 +1,17 @@
 # Template file for 'waylock'
 pkgname=waylock
-version=0.3.5
+version=0.6.2
 revision=1
-build_style=cargo
-hostmakedepends="pkg-config"
-makedepends="libxkbcommon-devel pam-devel"
+build_style=zig-build
+configure_args="-Dpie -Dstrip"
+hostmakedepends="pkg-config wayland-devel"
+makedepends="libxkbcommon-devel pam-devel wayland-protocols wayland-devel scdoc"
 short_desc="Simple screenlocker for wayland compositors"
 maintainer="Isaac Freund <ifreund@ifreund.xyz>"
-license="MIT"
+license="ISC"
 homepage="https://github.com/ifreund/waylock"
-distfiles="${homepage}/archive/v${version}.tar.gz"
-checksum=60abf78ae8aa9c28f3230f157607fbd74250a51322776ad1b7abed1408432b87
+distfiles="https://github.com/ifreund/waylock/releases/download/v${version}/waylock-${version}.tar.gz"
+checksum=4a794dedd1b11f3b9bb7b46f8a93c20aac5ac1d40a851cabaa7ae84fd36686fa
 
 post_install() {
 	vlicense LICENSE

  parent reply	other threads:[~2023-03-31 18:37 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 15:08 [PR PATCH] " dkwo
2023-03-31 15:17 ` icp1994
2023-03-31 15:22 ` [PR PATCH] [Updated] " dkwo
2023-03-31 15:30 ` icp1994
2023-03-31 18:37 ` dkwo [this message]
2023-03-31 18:38 ` dkwo
2023-03-31 23:45 ` [PR REVIEW] " ifreund
2023-03-31 23:45 ` ifreund
2023-03-31 23:45 ` ifreund
2023-03-31 23:45 ` ifreund
2023-03-31 23:45 ` ifreund
2023-04-01 11:01 ` classabbyamp
2023-04-01 12:27 ` ifreund
2023-04-01 14:09 ` [PR PATCH] [Updated] " dkwo
2023-04-01 14:10 ` [PR REVIEW] " dkwo
2023-04-01 14:10 ` dkwo
2023-04-01 14:10 ` dkwo
2023-04-01 14:11 ` dkwo
2023-04-01 14:13 ` dkwo
2023-04-01 14:14 ` dkwo
2023-04-01 14:15 ` [PR PATCH] [Updated] " dkwo
2023-04-01 14:16 ` [PR REVIEW] " dkwo
2023-04-01 16:49 ` paper42
2023-04-01 17:08 ` classabbyamp
2023-04-01 17:29 ` icp1994
2023-04-01 17:32 ` classabbyamp
2023-04-02  0:04 ` [PR REVIEW] " dkwo
2023-04-02  0:07 ` [PR PATCH] [Updated] " dkwo
2023-04-02 12:36 ` [PR REVIEW] " dkwo
2023-04-02 12:41 ` dkwo
2023-04-02 13:12 ` paper42
2023-04-03  0:42 ` [PR PATCH] [Updated] " dkwo
2023-04-03  0:52 ` dkwo
2023-04-03  0:58 ` dkwo
2023-04-03  7:45 ` paper42
2023-04-06 16:35 ` [PR PATCH] [Merged]: " paper42

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=20230331183750.AvtT0pss9oXldobZbkw8HLJe_n_KuYfV-XfTqSQFPSI@z \
    --to=dkwo@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).