From: fvalasiad <fvalasiad@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] wine: add aarch64 packaging
Date: Sat, 20 Apr 2024 23:45:59 +0200 [thread overview]
Message-ID: <20240420214559.E565622076@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49943@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 740 bytes --]
New comment by fvalasiad on void-packages repository
https://github.com/void-linux/void-packages/pull/49943#issuecomment-2067789419
Comment:
Hmm, will that allow for users to run wine with the experimental wayland support, or will it completely replace the x11 client? In the latter case maybe we should wait it out.
Could be a separate PR too if it isn't related with this.
And by WoW64 you mean the new version released in wine 9.0? With built-in support for 32bit binaries? If so, that's only enabled for musl currently, as it's also experimental. Musl had no 32bit wine so it was a good candidate to test. Would be great if people that use it reported if they had any issues so we could get going with applying it to glibc too.
next prev parent reply other threads:[~2024-04-20 21:45 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-20 20:47 [PR PATCH] " iFoundSilentHouse
2024-04-20 20:53 ` [PR REVIEW] " classabbyamp
2024-04-20 20:53 ` classabbyamp
2024-04-20 20:53 ` classabbyamp
2024-04-20 20:53 ` classabbyamp
2024-04-20 20:56 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-04-20 20:56 ` fvalasiad
2024-04-20 21:04 ` [PR REVIEW] " Calandracas606
2024-04-20 21:04 ` iFoundSilentHouse
2024-04-20 21:06 ` fvalasiad
2024-04-20 21:13 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-04-20 21:17 ` iFoundSilentHouse
2024-04-20 21:24 ` iFoundSilentHouse
2024-04-20 21:34 ` [PR REVIEW] " classabbyamp
2024-04-20 21:35 ` classabbyamp
2024-04-20 21:36 ` iFoundSilentHouse
2024-04-20 21:37 ` iFoundSilentHouse
2024-04-20 21:41 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-04-20 21:42 ` iFoundSilentHouse
2024-04-20 21:44 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-04-20 21:45 ` iFoundSilentHouse
2024-04-20 21:45 ` fvalasiad [this message]
2024-04-20 21:56 ` iFoundSilentHouse
2024-04-20 22:08 ` fvalasiad
2024-04-20 22:16 ` iFoundSilentHouse
2024-04-20 22:34 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-04-20 22:36 ` [PR REVIEW] " iFoundSilentHouse
2024-04-20 22:38 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-04-21 0:01 ` fvalasiad
2024-04-21 5:56 ` Hoshpak
2024-04-21 6:29 ` iFoundSilentHouse
2024-04-21 6:37 ` iFoundSilentHouse
2024-04-21 7:34 ` iFoundSilentHouse
2024-04-21 14:14 ` fvalasiad
2024-04-22 8:23 ` [PR PATCH] [Closed]: " iFoundSilentHouse
2024-04-22 8:23 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-04-22 8:25 ` iFoundSilentHouse
2024-04-22 10:34 ` iFoundSilentHouse
2024-04-22 10:37 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-04-22 10:39 ` iFoundSilentHouse
2024-04-22 10:44 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-04-22 10:49 ` iFoundSilentHouse
2024-04-22 11:53 ` iFoundSilentHouse
2024-04-22 11:54 ` iFoundSilentHouse
2024-04-22 12:09 ` iFoundSilentHouse
2024-04-22 12:09 ` iFoundSilentHouse
2024-04-22 12:10 ` iFoundSilentHouse
2024-04-22 12:12 ` iFoundSilentHouse
2024-04-22 12:13 ` iFoundSilentHouse
2024-04-22 12:17 ` iFoundSilentHouse
2024-04-22 13:24 ` zlice
2024-04-22 13:27 ` zlice
2024-04-22 16:35 ` Hoshpak
2024-04-22 16:49 ` iFoundSilentHouse
2024-04-22 16:50 ` iFoundSilentHouse
2024-04-22 17:01 ` iFoundSilentHouse
2024-04-22 19:52 ` fvalasiad
2024-04-23 8:04 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-04-23 8:07 ` iFoundSilentHouse
2024-04-23 8:13 ` iFoundSilentHouse
2024-04-23 9:18 ` iFoundSilentHouse
2024-04-25 17:39 ` iFoundSilentHouse
2024-05-14 3:30 ` zlice
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=20240420214559.E565622076@inbox.vuxu.org \
--to=fvalasiad@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).