From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: libretro-mupen64plus: update to 20190611
Date: Sat, 15 Jun 2019 14:43:25 +0200 [thread overview]
Message-ID: <20190615124325.LxVmsBkPLdGYXugcOPnO306OjKvUkrl8hE-0xhjpJHw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12400@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 916 bytes --]
There's a merged pull request on the void-packages repository
libretro-mupen64plus: update to 20190611
https://github.com/void-linux/void-packages/pull/12400
Description: Our 2015something version is aging and I don't think it's worth it to do any more fixes on it, especially considering there have been many commits upstream since and updating also allows building on ppc platforms and so on. However, there are no releases, ever, so trying a github commit snapshot (dunno if that's the right thing to do, but it can't be worse than using a random netbsd distfile...)
I also wonder if the default `rpi` option for armv6/7 is right, as that will make it not work on anything but... rpi, which is not exactly a generic target, we have many different ones now. Maybe we should switch that to standard mesa opengl. Thoughts?
I tested cross-compiling to aarch64, but not the others. I'll let the CI handle that.
prev parent reply other threads:[~2019-06-15 12:43 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 15:53 [PR PATCH] " voidlinux-github
2019-06-11 15:54 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-11 15:54 ` voidlinux-github
2019-06-11 16:20 ` voidlinux-github
2019-06-11 16:20 ` voidlinux-github
2019-06-11 16:21 ` voidlinux-github
2019-06-11 16:41 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-11 16:41 ` voidlinux-github
2019-06-11 16:42 ` voidlinux-github
2019-06-11 17:02 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-11 17:02 ` voidlinux-github
2019-06-11 17:03 ` voidlinux-github
2019-06-11 17:25 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-11 17:25 ` voidlinux-github
2019-06-11 17:33 ` voidlinux-github
2019-06-11 17:33 ` voidlinux-github
2019-06-11 17:33 ` voidlinux-github
2019-06-11 17:36 ` voidlinux-github
2019-06-11 17:44 ` voidlinux-github
2019-06-11 17:51 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-11 17:51 ` voidlinux-github
2019-06-11 18:50 ` voidlinux-github
2019-06-11 19:36 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-11 19:36 ` voidlinux-github
2019-06-11 19:36 ` voidlinux-github
2019-06-11 19:58 ` voidlinux-github
2019-06-11 20:25 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-11 20:25 ` voidlinux-github
2019-06-11 21:06 ` voidlinux-github
2019-06-11 21:06 ` voidlinux-github
2019-06-11 21:06 ` voidlinux-github
2019-06-11 21:06 ` voidlinux-github
2019-06-11 21:08 ` voidlinux-github
2019-06-15 12:43 ` voidlinux-github [this message]
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=20190615124325.LxVmsBkPLdGYXugcOPnO306OjKvUkrl8hE-0xhjpJHw@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).