From: Eloitor <Eloitor@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] fswatch: update to 1.18.2, adopt.
Date: Sat, 01 Feb 2025 08:53:48 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-54170@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 492 bytes --]
There is a new pull request by Eloitor against master on the void-packages repository
https://github.com/Eloitor/void-packages fswatch
https://github.com/void-linux/void-packages/pull/54170
fswatch: update to 1.18.2, adopt.
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### 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/54170.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-fswatch-54170.patch --]
[-- Type: text/x-diff, Size: 1294 bytes --]
From 657132e9fbab789a364a53262c9ba2a76553ae17 Mon Sep 17 00:00:00 2001
From: Eloi Torrents <eloitor@disroot.org>
Date: Sat, 1 Feb 2025 07:39:15 +0100
Subject: [PATCH] fswatch: update to 1.18.2, adopt.
---
srcpkgs/fswatch/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/fswatch/template b/srcpkgs/fswatch/template
index 8d5da88814ef49..e45506f71fd061 100644
--- a/srcpkgs/fswatch/template
+++ b/srcpkgs/fswatch/template
@@ -1,17 +1,17 @@
# Template file for 'fswatch'
pkgname=fswatch
-version=1.17.1
+version=1.18.2
revision=1
build_style=gnu-configure
configure_args="--disable-static"
hostmakedepends="doxygen"
short_desc="Cross-platform file change monitor with multiple backends"
-maintainer="Orphaned <orphan@voidlinux.org>"
+maintainer="Eloi Torrents <eloitor@duck.com>"
license="GPL-3.0-or-later"
homepage="https://emcrisostomo.github.io/fswatch/"
changelog="https://github.com/emcrisostomo/fswatch/raw/master/NEWS"
distfiles="https://github.com/emcrisostomo/fswatch/releases/download/${version}/fswatch-${version}.tar.gz"
-checksum=c38e341c567f5f16bfa64b72fc48bba5e93873d8572522e670e6f320bbc2122f
+checksum=1e5ec35c0bd8f39d45cb326e85362a0472e6b6b5a65eca7934c357e54926dfeb
post_install() {
rm -vr -- "${DESTDIR}/usr/share/doc"
next reply other threads:[~2025-02-01 7:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-01 7:53 Eloitor [this message]
2025-02-18 3:45 ` [PR PATCH] [Closed]: " classabbyamp
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-54170@inbox.vuxu.org \
--to=eloitor@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).