From: Andreas Rottmann <mail@r0tty.org>
To: guix-devel@gnu.org
Subject: Re: Rust packaging coordination
Date: Sat, 01 Feb 2020 17:05:07 +0100 [thread overview]
Message-ID: <87zhe2mgy4.fsf@londo.h.r0tty.org> (raw)
In-Reply-To: CAKf5CqXBPoc8Dvz1nLjjbaFp_c7D54XF+Ygr2eTRSzmWFvO4cw@mail.gmail.com
John Soo <jsoo1@asu.edu> writes:
> Hi rust packagers,
>
> We have: ripgrep, tokei, cbindgen.
>
> [ ... exa and alacritty ]
>
> I also have: racer, rustfmt, fd and pijul.
>
> What should we do next?
>
I have started packaging i3status-rust[1]. This is motivated primarily
by scratching my own itch, and to become more familiar with Guix
packaging. I'm still in the process of import-ing the required
dependencies; some notes so far:
- The dependency tree includes a portion of Rusts async universe not yet
packaged, `rust-futures-0.3` and `rust-tokio-0.2`. Preview versions of
the latter are already packaged -- there should probably be an effort
to update their reverse dependencies and switch to the "release"
versions of those.
- It includes bindings for libpulse (`rust-libpulse-bindings`),
inotify (`rust-inotify`), and libdbus (`rust-dbus`).
- I've encountered two crates with a not-already-defined license,
namely "0BSD" (`maildir` and `mailparse`). I've "faked" it for now with:
(define license:bsd-0
(license:fsf-free "https://spdx.org/licenses/0BSD.html"
"BSD Zero Clause License"))
The so-far accumulated list of crates from crates.io is:
rust-assert-matches-1.3
rust-chrono-tz-0.5
rust-cpuprofiler
rust-dbus
rust-futures-0.3
rust-futures-channel-0.3
rust-futures-core-0.3
rust-futures-executor-0.3
rust-futures-io-0.3
rust-futures-macro-0.3
rust-futures-sink-0.3
rust-futures-task-0.3
rust-futures-util-0.3
rust-i3ipc
rust-inotify-0.8
rust-inotify-sys-0.1
rust-libdbus-sys
rust-libpulse-binding-2
rust-libpulse-sys-1
rust-maildir-0.3
rust-mailparse-0.10
rust-notmuch-0.6
rust-parse-zoneinfo
rust-progress-0.2
rust-supercow-0.1
rust-tokio-0.2
If someone wants to tackle any of these, don't hold off; I don't know
how long I'll take until I actually can build `i3status-rust`. Once I
get to that point, I know that my package definitions are not totally
broken, and will try to turn them into patches.
[1]: https://github.com/greshake/i3status-rust
next prev parent reply other threads:[~2020-02-01 16:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 8:14 Rust packaging coordination John Soo
2020-01-18 16:48 ` Martin Becze
2020-01-18 16:55 ` John Soo
2020-01-18 17:20 ` Martin Becze
2020-01-18 17:37 ` John Soo
2020-01-19 10:09 ` Efraim Flashner
2020-01-21 16:26 ` John Soo
2020-01-27 15:09 ` John Soo
2020-01-30 16:59 ` Martin Becze
2020-01-31 18:45 ` John Soo
2020-02-01 16:05 ` Andreas Rottmann [this message]
2020-02-01 18:11 ` John Soo
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=87zhe2mgy4.fsf@londo.h.r0tty.org \
--to=mail@r0tty.org \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.