From: Hoshpak <Hoshpak@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: wine: update to 9.0
Date: Thu, 18 Jan 2024 18:03:00 +0100 [thread overview]
Message-ID: <20240118170300.56B3023258@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48249@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 989 bytes --]
New comment by Hoshpak on void-packages repository
https://github.com/void-linux/void-packages/pull/48249#issuecomment-1898873936
Comment:
@fvalasiad Regarding the libwine package: Please also remove the symlink. The package should probably also declare a "replaces=libwine>=0" to ensure that it is removed during the installation of the new wine version. I think that should solve the failing check.
Getting a package to cross-compile that isn't intended to be (I'm not sure if that's actually the case for wine) can be quite challenging so I would suggest that we give it a try and do if it's a quick wine but regard it as optional and postpone it if it's not to not delay the update unnecessarily. I would have some time on the weekend to try to adapt the template to cross-compile.
Regarding the enabling the new WoW64 for musl only for now, I think that that's a great idea. musl indeed never had support for 32 bit binaries so it would be a great benefit for musl users.
next prev parent reply other threads:[~2024-01-18 17:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 15:10 [PR PATCH] " fvalasiad
2024-01-17 15:14 ` [PR PATCH] [Updated] " fvalasiad
2024-01-17 15:17 ` fvalasiad
2024-01-17 17:20 ` [PR REVIEW] " Hoshpak
2024-01-17 17:20 ` Hoshpak
2024-01-17 17:29 ` [PR PATCH] [Updated] " fvalasiad
2024-01-17 17:30 ` [PR REVIEW] " fvalasiad
2024-01-17 17:31 ` fvalasiad
2024-01-17 17:34 ` Hoshpak
2024-01-17 17:42 ` fvalasiad
2024-01-18 13:12 ` AlexKurisu
2024-01-18 14:38 ` fvalasiad
2024-01-18 14:40 ` fvalasiad
2024-01-18 14:58 ` AlexKurisu
2024-01-18 17:03 ` Hoshpak [this message]
2024-01-18 17:03 ` Hoshpak
2024-01-18 17:03 ` Hoshpak
2024-01-18 17:33 ` [PR PATCH] [Updated] " fvalasiad
2024-01-18 17:36 ` fvalasiad
2024-01-18 18:04 ` fvalasiad
2024-01-19 23:14 ` [PR PATCH] [Updated] " fvalasiad
2024-01-19 23:41 ` fvalasiad
2024-01-20 8:57 ` [PR PATCH] [Merged]: " Hoshpak
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=20240118170300.56B3023258@inbox.vuxu.org \
--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).