From: jeff-hughes <jeff-hughes@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] New package: shellcaster-1.0.1
Date: Wed, 02 Dec 2020 21:04:52 +0100 [thread overview]
Message-ID: <20201202200452.XwLinibIDu6nOYBm2SBF4h7DU6lii4ifIjBPX46k76Y@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24525@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2017 bytes --]
New comment by jeff-hughes on void-packages repository
https://github.com/void-linux/void-packages/pull/24525#issuecomment-737464650
Comment:
Hi there -- shellcaster maintainer here. I'd love to make it available for Void Linux and for ARM as well. Yes, in hindsight relying on `pancurses` and `ncurses-rs` was a bad idea; I didn't notice that the projects are not very active. Long-term I may try to move to `termion` instead to remove the ncurses dependency, but that would require a fairly large rewrite.
Forking the `ncurses-rs` library to merge the [open PR for building on arm64](https://github.com/jeaye/ncurses-rs/pull/194/commits) would be an option, and I'm happy to jump to this dependency as long as it doesn't impact building on x86. However, to publish shellcaster on crates.io (which allows for easy installation with `cargo install shellcaster`), all the deps need to be on crates.io as well. I don't feel comfortable becoming the maintainer of a forked ARM-compatible `ncurses-rs`/`pancurses` library on crates.io if I don't even have an ARM device myself to test things on. If there is someone willing to do that, that would be great, and I'd happily switch dependencies.
The other option is that I can add a [git dependency](https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#multiple-locations) in my Cargo.toml, which will mean it will build `ncurses-rs` from the crates.io version when installing from crates.io, and build it from the Github repo when compiled from source. It's a little bit of a hack, but if I end up being the one forking those projects, that's ideal for me, as it doesn't set me up as some sort of "official" ncurses fork -- the scope is restricted to shellcaster.
Anyway, I wanted to check in here to figure out what would work best. Thanks, @kotajacob, for letting me know this existed. @fosslinux, you mention you're doing something with `ncurses-rs` -- what does that entail? If it's something I can help with in some way, I'd be happy to.
next prev parent reply other threads:[~2020-12-02 20:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 19:49 [PR PATCH] " daniel-eys
2020-08-28 21:03 ` ericonr
2020-08-28 21:44 ` daniel-eys
2020-08-28 22:07 ` ericonr
2020-08-28 23:09 ` daniel-eys
2020-08-29 22:14 ` [WIP] " fosslinux
2020-08-30 1:32 ` ericonr
2020-08-30 1:34 ` ericonr
2020-08-30 3:53 ` fosslinux
2020-08-30 12:21 ` daniel-eys
2020-08-30 23:18 ` fosslinux
2020-11-30 21:18 ` kotajacob
2020-12-02 20:04 ` jeff-hughes [this message]
2020-12-02 21:59 ` fosslinux
2021-07-12 19:53 ` [PR PATCH] [Closed]: " daniel-eys
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=20201202200452.XwLinibIDu6nOYBm2SBF4h7DU6lii4ifIjBPX46k76Y@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).