From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: New package: TheForceEngine-1.09.530
Date: Sat, 30 Sep 2023 00:44:15 +0200 [thread overview]
Message-ID: <20230929224415.LeFLH7Dp1a1FoH_XYwoWa3GgvrzvKgcIcUJ7tkd7ugU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45745@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1871 bytes --]
There's a merged pull request on the void-packages repository
New package: TheForceEngine-1.09.530
https://github.com/void-linux/void-packages/pull/45745
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
https://github.com/luciusDXL/TheForceEngine
* Requires `rtmidi` to get bumped to `5.0.0`, but I went ahead and bumped it to `6.0.0`. The license changed, but I think most of the other changes are features.
* I revbumped the other packages that require `rtmidi`. `milkytracker` needed `pkg-config` added to `hostmakedepends`, otherwise it would fail. I packaged all of them, but I only installed milkytracker and played around with it a little.
* 32bit seems to not be available for now for this package. According to some github issues, ARM support may be possible with some patches. I also tested musl x86_64 and it failed, but possibly would work with some patches.
* Notably during testing the shareware version of Dark Forces will not work with TheForceEngine, you must use the full game.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture, x86_64
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- i686 (failed)
- x86_64-musl (failed)
next prev parent reply other threads:[~2023-09-29 22:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 21:00 [PR PATCH] New package: TheForceEngine-1.09.410 kedodrill
2023-08-25 14:54 ` [PR REVIEW] " Chocimier
2023-08-25 14:54 ` Chocimier
2023-08-25 19:47 ` kedodrill
2023-08-25 19:49 ` kedodrill
2023-08-25 21:47 ` [PR PATCH] [Updated] " kedodrill
2023-09-28 5:00 ` kedodrill
2023-09-28 5:22 ` [PR PATCH] [Updated] New package: TheForceEngine-1.09.530 kedodrill
2023-09-28 7:43 ` Johnnynator
2023-09-28 7:43 ` [PR REVIEW] " Johnnynator
2023-09-28 7:44 ` Johnnynator
2023-09-28 7:44 ` Johnnynator
2023-09-28 7:45 ` Johnnynator
2023-09-28 22:56 ` kedodrill
2023-09-28 22:56 ` kedodrill
2023-09-28 22:57 ` [PR REVIEW] " kedodrill
2023-09-29 11:23 ` Johnnynator
2023-09-29 20:04 ` [PR PATCH] [Updated] " kedodrill
2023-09-29 20:04 ` kedodrill
2023-09-29 22:44 ` Johnnynator
2023-09-29 22:44 ` Johnnynator [this message]
2023-09-30 0:58 ` kedodrill
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=20230929224415.LeFLH7Dp1a1FoH_XYwoWa3GgvrzvKgcIcUJ7tkd7ugU@z \
--to=johnnynator@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).