From: Vinfall <Vinfall@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] retroarch: update to 1.14.0
Date: Fri, 27 Jan 2023 10:54:28 +0100 [thread overview]
Message-ID: <20230127095428.51pV8TKN8smju1nOzVbDi1XkMf-obj5UsbymdaqpwUo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41899@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
There is an updated pull request by Vinfall against master on the void-packages repository
https://github.com/Vinfall/void-packages retroarch-update
https://github.com/void-linux/void-packages/pull/41899
retroarch: update to 1.14.0
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
- I built this PR locally for this architecture:
- armv6l-musl (crossbuild)
A patch file from https://github.com/void-linux/void-packages/pull/41899.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-retroarch-update-41899.patch --]
[-- Type: text/x-diff, Size: 1249 bytes --]
From 6b07ccff5b0bc62ca1765e7b5fc39c72f1581f10 Mon Sep 17 00:00:00 2001
From: Vinfall <neptuniahuai0tc@riseup.net>
Date: Fri, 27 Jan 2023 17:53:54 +0800
Subject: [PATCH] retroarch: update to 1.4.0
---
srcpkgs/retroarch/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/retroarch/template b/srcpkgs/retroarch/template
index 9033ba001ca6..240d3df9db00 100644
--- a/srcpkgs/retroarch/template
+++ b/srcpkgs/retroarch/template
@@ -1,6 +1,6 @@
# Template file for 'retroarch'
pkgname=retroarch
-version=1.13.0
+version=1.14.0
revision=1
build_style=configure
configure_args="--prefix=/usr --sysconfdir=/etc --enable-networking
@@ -24,7 +24,7 @@ license="GPL-3.0-or-later"
homepage="https://www.retroarch.com/"
changelog="https://raw.githubusercontent.com/libretro/RetroArch/master/CHANGES.md"
distfiles="https://github.com/libretro/RetroArch/archive/v$version.tar.gz"
-checksum=7f33bfb821440b2e30eb6c9d63eb4e2da1d2910ae90b43f691e3c28759739710
+checksum=aa4d579bfceb43450725171f594f69877f007a8892cb46678f8b62935c4de635
build_options="ffmpeg flac glcore gles2 glslang jack neon pulseaudio qt5 sdl2 vulkan wayland x11"
build_options_default="ffmpeg flac glcore glslang pulseaudio sdl2 vulkan wayland x11"
next prev parent reply other threads:[~2023-01-27 9:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 8:04 [PR PATCH] " Vinfall
2023-01-27 9:54 ` Vinfall [this message]
2023-01-29 22:31 ` classabbyamp
2023-01-30 2:44 ` Vinfall
2023-01-30 2:54 ` classabbyamp
2023-01-30 3:00 ` Vinfall
2023-01-30 3:01 ` Vinfall
2023-01-30 3:03 ` classabbyamp
2023-01-30 3:04 ` [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=20230127095428.51pV8TKN8smju1nOzVbDi1XkMf-obj5UsbymdaqpwUo@z \
--to=vinfall@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).