From: iFoundSilentHouse <iFoundSilentHouse@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] dwm: update to 6.5.
Date: Fri, 22 Mar 2024 22:42:06 +0100 [thread overview]
Message-ID: <20240322214206.D8A6822851@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49449@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1754 bytes --]
There is an updated pull request by iFoundSilentHouse against master on the void-packages repository
https://github.com/iFoundSilentHouse/void-packages dwm-6.5
https://github.com/void-linux/void-packages/pull/49449
dwm: update to 6.5.
<!-- 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**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
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, (x86_64)
- I built this PR locally for these architectures:
- x86_64-musl
- i686
- aarch64
I use dwm on a daily basis. Now I'm gonna make custom dwm build based on xbps-src to always test it. Already subscribed to suckless rss so I won't skip update. I know that I did strange things in this repo: PR'd single bash script, PR'd synth with questionable licensing (my apologies ahesford. You're right about that). But as for dwm: I understand how it works as a program, how it works together with xbps-src and I can maintain it efficently, even make patches/rebuilds if it's needed. And I do want to help my with favorite distro the way I can.
A patch file from https://github.com/void-linux/void-packages/pull/49449.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-dwm-6.5-49449.patch --]
[-- Type: text/x-diff, Size: 1039 bytes --]
From 0183fc5c540417080a07901223c5300b26dd7856 Mon Sep 17 00:00:00 2001
From: IFoundSilentHouse <adeptslab@gmail.com>
Date: Fri, 22 Mar 2024 17:21:37 +0600
Subject: [PATCH] dwm: update to 6.5.
---
srcpkgs/dwm/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/dwm/template b/srcpkgs/dwm/template
index b0e801fe992bed..3fc2498e7a1e35 100644
--- a/srcpkgs/dwm/template
+++ b/srcpkgs/dwm/template
@@ -1,6 +1,6 @@
# Template file for 'dwm'
pkgname=dwm
-version=6.4
+version=6.5
revision=1
makedepends="libXinerama-devel libXft-devel freetype-devel"
short_desc="Dynamic window manager for X"
@@ -8,7 +8,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
license="MIT"
homepage="https://dwm.suckless.org"
distfiles="https://dl.suckless.org/dwm/dwm-${version}.tar.gz"
-checksum=fa9c0d69a584485076cfc18809fd705e5c2080dafb13d5e729a3646ca7703a6e
+checksum=21d79ebfa9f2fb93141836c2666cb81f4784c69d64e7f1b2352f9b970ba09729
do_build() {
[ -e ${FILESDIR}/config.h ] && cp ${FILESDIR}/config.h config.h
next prev parent reply other threads:[~2024-03-22 21:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 12:02 [PR PATCH] dwm: update to 6.5, adopt iFoundSilentHouse
2024-03-22 14:56 ` Duncaen
2024-03-22 14:57 ` Duncaen
2024-03-22 15:59 ` iFoundSilentHouse
2024-03-22 16:04 ` [PR PATCH] [Updated] dwm: update to 6.5 iFoundSilentHouse
2024-03-22 16:06 ` iFoundSilentHouse
2024-03-22 20:48 ` balejk
2024-03-22 21:42 ` iFoundSilentHouse [this message]
2024-03-23 17:23 ` [PR PATCH] [Merged]: " leahneukirchen
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=20240322214206.D8A6822851@inbox.vuxu.org \
--to=ifoundsilenthouse@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).