From: maybe-one-day-ubermensch <maybe-one-day-ubermensch@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] wf-recorder: update to 0.2.1
Date: Fri, 15 May 2020 00:37:55 +0200 [thread overview]
Message-ID: <20200514223755.6gT0TKtyfMh_2eDS8TsF1pztCMDZ3I1OLGgG28G9SuM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21977@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 363 bytes --]
There is an updated pull request by maybe-one-day-ubermensch against master on the void-packages repository
https://github.com/maybe-one-day-ubermensch/void-packages update-wf-recorder
https://github.com/void-linux/void-packages/pull/21977
wf-recorder: update to 0.2.1
A patch file from https://github.com/void-linux/void-packages/pull/21977.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update-wf-recorder-21977.patch --]
[-- Type: text/x-diff, Size: 1265 bytes --]
From f66605816cee8e4fe5be5ea925c746a85bf7a9e8 Mon Sep 17 00:00:00 2001
From: Jony <maybe-one-day-ubermensch@protonmail.com>
Date: Thu, 14 May 2020 15:19:44 -0700
Subject: [PATCH] wf-recorder: update to 0.2.1
---
srcpkgs/wf-recorder/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/wf-recorder/template b/srcpkgs/wf-recorder/template
index 31889991390..8ca26d6ef45 100644
--- a/srcpkgs/wf-recorder/template
+++ b/srcpkgs/wf-recorder/template
@@ -1,6 +1,6 @@
# Template file for 'wf-recorder'
pkgname=wf-recorder
-version=0.2
+version=0.2.1
revision=1
build_style=meson
hostmakedepends="pkg-config ninja scdoc wayland-devel"
@@ -11,11 +11,11 @@ maintainer="Jony <maybe-one-day-ubermensch@protonmail.com>"
license="MIT"
homepage="https://github.com/ammen99/wf-recorder"
distfiles="https://github.com/ammen99/${pkgname}/archive/v${version}.tar.gz"
-checksum=e35eef43920fc0492cd4702653b613b5ab1caaf070b5f0542db2f5c4d7a90deb
+checksum=45cf04cf58cf241c22fa2fbb70481a3747ad33e6930e4bdba7b9cc7018789ad1
# silly workaround to prevent vector/bool/etc from being defined
case "$XBPS_TARGET_MACHINE" in
- ppc*) CXXFLAGS+=" -D__APPLE_ALTIVEC__";;
+ ppc*) CXXFLAGS+=" -D__APPLE_ALTIVEC__";;
esac
post_install() {
next prev parent reply other threads:[~2020-05-14 22:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 22:23 [PR PATCH] " maybe-one-day-ubermensch
2020-05-14 22:37 ` maybe-one-day-ubermensch [this message]
2020-05-16 8:05 ` [PR PATCH] [Merged]: " jnbr
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=20200514223755.6gT0TKtyfMh_2eDS8TsF1pztCMDZ3I1OLGgG28G9SuM@z \
--to=maybe-one-day-ubermensch@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).