From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: SDL: replace with `sdl12-compat`
Date: Mon, 03 Feb 2025 20:36:31 +0100 [thread overview]
Message-ID: <20250203193631.A24BE23556@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-54199@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
There's a merged pull request on the void-packages repository
SDL: replace with `sdl12-compat`
https://github.com/void-linux/void-packages/pull/54199
Description:
Especially now that SDL 3 is available, let's completely abandon the dead SDL 1.2 in favor of the official compat library that uses SDL 2 on the backend. This supersedes https://github.com/void-linux/void-packages/pull/53761.
Four packages that depend on SDL fail to build because their distfiles cannot be fetched:
- `agg` (only required by `desumume`)
- `ballerburg` (leaf package, some game)
- `swars` (leaf package, only for `i686`, some game)
- `xrick` (leaf package, restricted)
I've marked these broken to highlight the existing issues. Note that, because `sdl12-compat` is ABI compatible with SDL 1.2, people with any of these packages installed should still be able to upgrade seamlessly and we should avoid any shlib staging.
#### Testing the changes
- I tested the changes in this PR: **briefly**, works as expected with `dosbox` and `tworld`.
prev parent reply other threads:[~2025-02-03 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 14:09 [PR PATCH] " ahesford
2025-02-03 14:15 ` [PR PATCH] [Updated] " ahesford
2025-02-03 19:36 ` ahesford
2025-02-03 19:36 ` ahesford [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=20250203193631.A24BE23556@inbox.vuxu.org \
--to=ahesford@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).