From: jeff-hughes <jeff-hughes@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: shellcaster
Date: Sat, 26 Feb 2022 21:56:33 +0100 [thread overview]
Message-ID: <20220226205633.PX-vX099FfFsuq6eOl9EZgNP23jbp55ehjSz_1Hz0ZI@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: 1089 bytes --]
New comment by jeff-hughes on void-packages repository
https://github.com/void-linux/void-packages/issues/26475#issuecomment-1052603386
Comment:
Hi folks, this may be long past the point where anybody still cares to package shellcaster for Void (I know there were a few PRs that ended up getting closed a while back), but I figured I'd add a note here anyway. I'm the developer of shellcaster, and I just released v2.0, which eliminates the ncurses dependency. This was something that was causing issues when trying to package it before (see [here](https://github.com/void-linux/void-packages/pull/24525)). The TUI solution is now Rust-native, and using the `crossterm` crate that is actively maintained, rather than `pancurses` and `ncurses-rs` which are largely unmaintained at this point.
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.
next prev parent reply other threads:[~2022-02-26 20:56 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 [this message]
2022-02-26 21:18 ` kawaiiamber
2022-02-26 21:19 ` kawaiiamber
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=20220226205633.PX-vX099FfFsuq6eOl9EZgNP23jbp55ehjSz_1Hz0ZI@z \
--to=jeff-hughes@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).