From: Hoshpak <Hoshpak@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: wine: Add wine-staging patchset as a (non-default) build option
Date: Thu, 14 Jan 2021 19:22:26 +0100 [thread overview]
Message-ID: <20210114182226.ZD44CFXA36B5aR4tLvKmjLdzQrIzgj5U0VZ-VdBqHMI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27791@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
There's a merged pull request on the void-packages repository
wine: Add wine-staging patchset as a (non-default) build option
https://github.com/void-linux/void-packages/pull/27791
Description:
Because staging is not release quality, this is introduced as a non-default build option. Because users expect a certain level of breakage and imperfection in Wine in general, I think it's still fine to introduce as an option, despite Void's policy against non-release software. Wine-staging is frequently required to make some applications/games work.
Open question of what to do if wine-staging lags a upstream wine release by a bit -- block package updates? But at least for the last several versions, wine-staging has tracked wine closely, lagging in their releases by no more than 1 day.
Builds on x86_64 and i686. Tested on x86_64 with wine+wine-32bit multi.
closes #27612
prev parent reply other threads:[~2021-01-14 18:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 20:07 [PR PATCH] " aeadio
2021-01-09 20:46 ` ericonr
2021-01-09 20:49 ` [PR PATCH] [Updated] " aeadio
2021-01-09 22:00 ` [PR REVIEW] wine: " Chocimier
2021-01-09 22:30 ` [PR PATCH] [Updated] " aeadio
2021-01-09 22:31 ` aeadio
2021-01-12 17:35 ` Hoshpak
2021-01-12 20:51 ` [PR PATCH] [Updated] " aeadio
2021-01-12 20:51 ` aeadio
2021-01-12 20:53 ` [PR PATCH] [Updated] " aeadio
2021-01-12 21:09 ` ericonr
2021-01-14 18:22 ` Hoshpak [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=20210114182226.ZD44CFXA36B5aR4tLvKmjLdzQrIzgj5U0VZ-VdBqHMI@z \
--to=hoshpak@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).