From: kawaiiamber <kawaiiamber@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: shellcaster
Date: Sat, 26 Feb 2022 22:19:49 +0100 [thread overview]
Message-ID: <20220226211949.XZ2rKGfgcDoVuOu3YcNa-DOIvQQMKYcnwY80Mm4orjg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26475@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
New comment by kawaiiamber on void-packages repository
https://github.com/void-linux/void-packages/issues/26475#issuecomment-1052629286
Comment:
All past three PRs for shellcaster have been closed: [27785](https://github.com/void-linux/void-packages/pull/27785), [24826](https://github.com/void-linux/void-packages/pull/24826), [24525](https://github.com/void-linux/void-packages/pull/24525)
I don't believe people are interested in packaging shellcaster anymore.
> I don't have an ARM device to test compilation on that architecture, but presumably there should be one less glaring issue in that regard. If there are further issues packaging for Void Linux that can be resolved upstream, I'm happy to work with you -- just open an issue and we can discuss.
You don't need one just to test the build. You can test different archs with the `-a` flag - see [CONTRIBUTING.md](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md). If you wanted to test ARM for exmaple: `./xbps-src pkg -a aarch64 shellcaster`. If you want to package your software for void, feel free to PR. If not, I can try maintaining it.
next prev parent reply other threads:[~2022-02-26 21:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 9:36 [ISSUE] " handow23
2021-01-09 15:40 ` kawaiiamber
2021-01-10 21:19 ` kawaiiamber
2022-02-26 20:56 ` jeff-hughes
2022-02-26 21:18 ` kawaiiamber
2022-02-26 21:19 ` kawaiiamber [this message]
2022-02-26 21:20 ` kawaiiamber
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=20220226211949.XZ2rKGfgcDoVuOu3YcNa-DOIvQQMKYcnwY80Mm4orjg@z \
--to=kawaiiamber@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).