From: Jjp137 <Jjp137@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gzdoom: update to version 4.10.0.
Date: Mon, 03 Jul 2023 23:45:54 +0200 [thread overview]
Message-ID: <20230703214554.LlYjNOH6LURBCfvqbg9lbXGO3t_OdLmfye4EjBFwIYQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44504@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
New comment by Jjp137 on void-packages repository
https://github.com/void-linux/void-packages/pull/44504#issuecomment-1619183112
Comment:
> but it seems that they no longer want to support i686
Yeah, as someone casually following the Doom community, that has been the plan for some time. I usually just watch this repo occasionally from afar since I started trying out Void Linux on my laptop, but as a GZDoom user (albeit in another distro), I saw this PR and I wanted to give some more context.
In particular, see this commit and the comments below it: https://github.com/ZDoom/gzdoom/commit/8c244f6f850eeb5a5dede7f887f3f1ba87b3d8bc
A few years ago, there was a thread about 32-bit support here in which many users think that 32-bit is dead: https://forum.zdoom.org/viewtopic.php?p=1134388
Thus, if one uses a 32-bit build of GZDoom and problems happen, they should not expect support from upstream. The hardware requirements for GZDoom have always been steadily increasing throughout the years (one notable example is dropping OpenGL 2.1 support many years ago), and this is just another example of it.
next prev parent reply other threads:[~2023-07-03 21:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 15:21 [PR PATCH] " SpidFightFR
2023-06-18 15:37 ` SpidFightFR
2023-07-01 14:48 ` classabbyamp
2023-07-01 15:13 ` [PR REVIEW] " classabbyamp
2023-07-02 8:12 ` [PR PATCH] [Updated] " SpidFightFR
2023-07-02 8:14 ` [PR REVIEW] " SpidFightFR
2023-07-02 8:26 ` SpidFightFR
2023-07-02 8:33 ` [PR PATCH] [Updated] " SpidFightFR
2023-07-02 8:50 ` [PR REVIEW] " SpidFightFR
2023-07-03 21:45 ` Jjp137 [this message]
2023-07-03 22:05 ` classabbyamp
2023-07-03 22:05 ` classabbyamp
2023-07-03 22:05 ` classabbyamp
2023-07-04 15:09 ` [PR PATCH] [Updated] " SpidFightFR
2023-07-04 22:26 ` [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=20230703214554.LlYjNOH6LURBCfvqbg9lbXGO3t_OdLmfye4EjBFwIYQ@z \
--to=jjp137@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).