From: maybe-one-day-ubermensch <maybe-one-day-ubermensch@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] wf-recorder: update to 0.3.0.
Date: Fri, 01 Jul 2022 21:55:01 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37794@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 545 bytes --]
There is a new pull request by maybe-one-day-ubermensch against master on the void-packages repository
https://github.com/maybe-one-day-ubermensch/void-packages wf-recorder
https://github.com/void-linux/void-packages/pull/37794
wf-recorder: update to 0.3.0.
#### Testing the changes
- I tested the changes in this PR: **briefly**
openCL support was [dropped](https://github.com/ammen99/wf-recorder/commit/385b0158238dc914de17d17761e17cdbc74cbfef).
A patch file from https://github.com/void-linux/void-packages/pull/37794.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-wf-recorder-37794.patch --]
[-- Type: text/x-diff, Size: 1369 bytes --]
From e9a4400b52a65843430648015704bbe66241350d Mon Sep 17 00:00:00 2001
From: Jony <maybe-one-day-ubermensch@protonmail.com>
Date: Fri, 1 Jul 2022 12:42:25 -0700
Subject: [PATCH] wf-recorder: update to 0.3.0.
---
srcpkgs/wf-recorder/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/wf-recorder/template b/srcpkgs/wf-recorder/template
index 8ca26d6ef458..e278eb001600 100644
--- a/srcpkgs/wf-recorder/template
+++ b/srcpkgs/wf-recorder/template
@@ -1,17 +1,17 @@
# Template file for 'wf-recorder'
pkgname=wf-recorder
-version=0.2.1
+version=0.3.0
revision=1
build_style=meson
-hostmakedepends="pkg-config ninja scdoc wayland-devel"
+hostmakedepends="pkg-config scdoc wayland-devel"
makedepends="wayland-protocols wayland-devel ffmpeg-devel x264-devel
- pulseaudio-devel ocl-icd-devel"
+ pulseaudio-devel"
short_desc="Screen recorder for wlroots-based compositors"
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=45cf04cf58cf241c22fa2fbb70481a3747ad33e6930e4bdba7b9cc7018789ad1
+checksum=3af1e933872653233d87167bab73d96f984d00e995385190b586be4d89dbbfdf
# silly workaround to prevent vector/bool/etc from being defined
case "$XBPS_TARGET_MACHINE" in
next reply other threads:[~2022-07-01 19:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 19:55 maybe-one-day-ubermensch [this message]
2022-07-02 1:58 ` [PR PATCH] [Merged]: " 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-37794@inbox.vuxu.org \
--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).