all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Soo <jsoo1@asu.edu>
To: Andreas Rottmann <mail@r0tty.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Rust packaging coordination
Date: Sat, 1 Feb 2020 18:11:15 +0000	[thread overview]
Message-ID: <CAKf5CqUSrO_s=by-dUbOn+bBaSayU58WT_k32x_uOAHr+hkBTg@mail.gmail.com> (raw)
In-Reply-To: <87zhe2mgy4.fsf@londo.h.r0tty.org>

Hi Andreas and everyone,

Patches for exa are in #39382

> I have started packaging i3status-rust[1]. This is motivated primarily
> by scratching my own itch, and to become more familiar with Guix
> packaging.

Excellent! Welcome and have fun!

> - 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.

I would imagine that the package authors start using the release async soon.
The release of async seemed like a big deal in the rust community.

> - It includes bindings for libpulse (`rust-libpulse-bindings`),
>   inotify (`rust-inotify`), and libdbus (`rust-dbus`).

Oh that's good! Maybe those can go in sooner than i3status-rust.
Smaller batches with the async libraries, dbus and inotify seem pretty
likely to be reused.

> - 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"))

I'm not sure what to do for a new license, but that reminds me that
the importer doesn't understand the bsd-2 clause.

Thanks and happy hacking,

John

      reply	other threads:[~2020-02-01 18:11 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
2020-02-01 18:11           ` John Soo [this message]

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='CAKf5CqUSrO_s=by-dUbOn+bBaSayU58WT_k32x_uOAHr+hkBTg@mail.gmail.com' \
    --to=jsoo1@asu.edu \
    --cc=guix-devel@gnu.org \
    --cc=mail@r0tty.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.