all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Troy Figiel <troy@troyfigiel.com>
Cc: 68665-done@debbugs.gnu.org
Subject: bug#68665: [PATCH 00/12 rust-team] gnu: Add Rust dependencies of python-cramjam.
Date: Tue, 23 Jan 2024 16:36:12 +0200	[thread overview]
Message-ID: <Za_O3KTvDnd1dj5l@3900XT> (raw)
In-Reply-To: <87msswgvnm.fsf@troyfigiel.com>

[-- Attachment #1: Type: text/plain, Size: 1653 bytes --]

On Tue, Jan 23, 2024 at 12:02:21PM +0100, Troy Figiel wrote:
> Two short points:
> 
> 1. It seems I forgot to add my copyright. In the past I added it to
> crates-graphics.scm and not to crates-io.scm as I thought. I could add
> an additional 13th patch, or maybe it would be easier to include it in
> one of the other patches.

I've added it for you to crates-io, and also to rust-apps.

> 2. How is the cross-build-system depedency best handled? In the git logs
> I have found two merges of the rust branch into master (1 month and 9
> months ago), so if the merge happens once every ~6 months, it could be a
> long wait. I am not in any rush, but in the meantime it does block me
> from upstreaming other Python patches that depend on python-cramjam. If
> there is a better way to handle this, I would love to know.

We don't really have a target.  I figured every 3 months or so, enough
time to cover 2 rounds of rust version bumps, would probably be a good
cadence.  Checking qa.guix.gnu.org I don't see that anyone has asked for
a merge currently, which is about when I'd plan on jumping in.

In terms of goals for the branch currently, I'd like to make sure that
it re-adds support for riscv64 (up to 1.75 locally!) and try to figure
out the issue I'm having on ppc64le with building rust-1.73.  And also
move more packages out of crates-io to other modules, it's still over
3000.

Also, patches pushed.

-- 
Efraim Flashner   <efraim@flashner.co.il>   רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2024-01-23 14:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 23:01 [bug#68665] [PATCH 00/12 rust-team] gnu: Add Rust dependencies of python-cramjam Troy Figiel
2024-01-22 21:34 ` [bug#68665] [PATCH 03/12] gnu: rust-lz4-1: Update to 1.24.0 Troy Figiel
2024-01-22 21:34 ` [bug#68665] [PATCH 01/12] gnu: rust-lz4-sys-1: Update to 1.9.4 Troy Figiel
2024-01-22 21:34 ` [bug#68665] [PATCH 02/12] gnu: rust-lz4-sys-1: Don't skip the build Troy Figiel
2024-01-22 21:45 ` [bug#68665] [PATCH 04/12] gnu: rust-lz4-1: " Troy Figiel
2024-01-22 21:54 ` [bug#68665] [PATCH 05/12] gnu: rust-cbindgen-0.24: Update to 0.24.5 Troy Figiel
2024-01-22 22:01 ` [bug#68665] [PATCH 06/12] gnu: Add rust-target-lexicon-0.11 Troy Figiel
2024-01-22 22:08 ` [bug#68665] [PATCH 07/12] gnu: Add rust-libdeflate-sys-1 Troy Figiel
2024-01-22 22:12 ` [bug#68665] [PATCH 08/12] gnu: rust-libdeflate-sys-0.11: Inherit from rust-libdeflate-sys-1 Troy Figiel
2024-01-22 22:20 ` [bug#68665] [PATCH 09/12] gnu: Add rust-libdeflater-1 Troy Figiel
2024-01-22 22:27 ` [bug#68665] [PATCH 10/12] gnu: rust-libdeflater-0.11: Inherit from rust-libdeflater-1 Troy Figiel
2024-01-22 22:46 ` [bug#68665] [PATCH 11/12] gnu: Add rust-inline-c-macro-0.1 Troy Figiel
2024-01-22 22:54 ` [bug#68665] [PATCH 12/12] gnu: Add rust-inline-c-0.1 Troy Figiel
2024-01-23 11:02 ` [bug#68665] [PATCH 00/12 rust-team] gnu: Add Rust dependencies of python-cramjam Troy Figiel
2024-01-23 14:36   ` Efraim Flashner [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=Za_O3KTvDnd1dj5l@3900XT \
    --to=efraim@flashner.co.il \
    --cc=68665-done@debbugs.gnu.org \
    --cc=troy@troyfigiel.com \
    /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.