From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: srb2-2.2.6
Date: Sun, 21 Feb 2021 06:57:32 +0100 [thread overview]
Message-ID: <20210221055732.IauODMAj8x1RZt1TcDQ4J-XQNvmzyLCAwGiXO_Ysajg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21980@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 720 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/21980#issuecomment-782805534
Comment:
@Oreo639 if this is accepted, but as a restricted package (not a guarantee, just something I put forward), do you think you'd be up to updating it for new releases, or do you think you'll stick with the flatpak?
If you still want to maintain it, we can keep this open for further pondering, otherwise I believe we should close the PR. Distributing assets is rather messy, and I'm not sure the packaage is very useful without them, with just the executables. What do you think? For the record, we do ship a lot of doom clones and some other games which require external assets.
next prev parent reply other threads:[~2021-02-21 5:57 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 7:59 [PR PATCH] New package: srb2-2.2.4 Oreo639
2020-05-15 8:00 ` [PR PATCH] [Updated] " Oreo639
2020-05-15 8:42 ` Oreo639
2020-05-15 8:49 ` Oreo639
2020-05-15 8:59 ` Oreo639
2020-07-19 1:52 ` Oreo639
2020-07-19 2:54 ` Oreo639
2020-07-27 22:41 ` [PR PATCH] [Updated] New package: srb2-2.2.6 Oreo639
2020-07-27 23:04 ` Oreo639
2020-07-27 23:05 ` Oreo639
2021-02-16 6:23 ` [PR REVIEW] " ericonr
2021-02-16 6:24 ` ericonr
2021-02-16 6:24 ` ericonr
2021-02-16 19:51 ` [PR PATCH] [Updated] " Oreo639
2021-02-16 19:53 ` [PR REVIEW] " Oreo639
2021-02-16 19:53 ` Oreo639
2021-02-16 19:54 ` Oreo639
2021-02-16 19:54 ` ericonr
2021-02-16 19:58 ` Oreo639
2021-02-16 20:00 ` Oreo639
2021-02-16 20:00 ` Oreo639
2021-02-16 20:20 ` ericonr
2021-02-16 20:21 ` [PR PATCH] [Updated] " Oreo639
2021-02-16 20:21 ` [PR REVIEW] " Oreo639
2021-02-16 20:22 ` Oreo639
2021-02-16 20:31 ` ericonr
2021-02-16 20:31 ` ericonr
2021-02-16 21:14 ` Oreo639
2021-02-16 22:06 ` [PR PATCH] [Updated] " Oreo639
2021-02-16 22:07 ` [PR REVIEW] " Oreo639
2021-02-21 5:06 ` ericonr
2021-02-21 5:13 ` the-maldridge
2021-02-21 5:31 ` Oreo639
2021-02-21 5:32 ` Oreo639
2021-02-21 5:33 ` the-maldridge
2021-02-21 5:57 ` ericonr [this message]
2021-02-21 6:01 ` Oreo639
2021-02-21 8:18 ` Oreo639
2021-02-21 8:19 ` Oreo639
2021-02-21 8:19 ` Oreo639
2021-04-11 4:11 ` ericonr
2021-04-11 4:51 ` Oreo639
2021-04-11 20:21 ` [PR PATCH] [Updated] " Oreo639
2021-04-18 3:58 ` [PR PATCH] [Merged]: " ericonr
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=20210221055732.IauODMAj8x1RZt1TcDQ4J-XQNvmzyLCAwGiXO_Ysajg@z \
--to=ericonr@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).