unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: John Kehayias via Guix-patches via <guix-patches@gnu.org>
To: 57702@debbugs.gnu.org
Cc: paren@disroot.org, VesselWave@protonmail.com,
	Maxime Devos <maximedevos@telenet.be>,
	Mark H Weaver <mhw@netris.org>
Subject: [bug#57702] [PATCH 0/8] Update rust-clap-3 to 3.2.17
Date: Tue, 20 Sep 2022 19:31:08 +0000	[thread overview]
Message-ID: <878rmd6dxn.fsf@protonmail.com> (raw)
In-Reply-To: <G98-R4oRZx18Wfoj1cCmRwQhhwXpZzYD8_C4o8-BRO3dwClQP6GeV8_88JtlTBSvpd9W2J9qv3U-HXwnmVxgk9WnyOpvqn38nlbYm14JX8g=@protonmail.com>

Hi everyone,

Just dropping a note that many of these packages are required for the IceCat update that Mark has on the gnuzilla-updates branch. There, some version of the needed packages for newer rust (which is on staging already) and rust-cbindgen exist, which overlaps with the packages in this patch series. I also had contributed similar patches to another channel for building the latest of Firefox, which Mark used (along with other's work) for the IceCat update.

Anyway, just wanted to chime in so that this can be coordinated and avoid duplicated work. I only looked at this patch series quickly before, but I think many of the duplicate patches needed for cbindgen were similar across the different versions and should be straightforward to migrate to their proper package home outside of gnuzilla. Last I heard staging being merged to master was imminent, which will give us the newer rust compilers as well.

Let me know if there is something I can do to help.

John





      parent reply	other threads:[~2022-09-20 23:23 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09 14:18 [bug#57702] [PATCH 0/8] Update rust-clap-3 to 3.2.17 VesselWave via Guix-patches via
2022-09-09 16:03 ` [bug#57702] [PATCH v2 1/8] gnu: Add rust-unic-emoji-char-0.9 VesselWave via Guix-patches via
2022-09-09 20:30   ` ( via Guix-patches via
2022-09-09 20:33   ` ( via Guix-patches via
2022-09-09 16:04 ` [bug#57702] [PATCH v2 2/8] gnu: rust-textwrap: Add 0.15.0 VesselWave via Guix-patches via
2022-09-09 16:05 ` [bug#57702] [PATCH v2 3/8] gnu: rust-crossbeam-utils-0.8: Add development inputs VesselWave via Guix-patches via
2022-09-09 16:06 ` [bug#57702] [PATCH v2 4/8] gnu: rust-parking-lot-core: Inrerit from latest VesselWave via Guix-patches via
2022-09-09 16:09 ` [bug#57702] [PATCH v2 5/8] gnu: rust-once-cell-1: Update to 1.13.1 VesselWave via Guix-patches via
2022-09-09 16:10 ` [bug#57702] [PATCH v2 6/8] gnu: Add rust-clap-lex-0.2 VesselWave via Guix-patches via
2022-09-09 16:11 ` [bug#57702] [PATCH v2 7/8] gnu: rust-clap-derive-3: Update to 3.2.17 VesselWave via Guix-patches via
2022-09-09 16:12 ` [bug#57702] [PATCH v2 8/8] gnu: rust-clap-3: " VesselWave via Guix-patches via
2022-09-09 17:10 ` [bug#57702] [PATCH v2 0/8] " VesselWave via Guix-patches via
2022-09-09 18:05 ` [bug#57702] [PATCH 1/8] gnu: Add rust-unic-emoji-char-0.9 VesselWave via Guix-patches via
2022-09-10  0:13   ` Maxime Devos
2022-09-10  6:13 ` [bug#57702] [PATCH 2/8] gnu: rust-textwrap: Add 0.15.0 VesselWave via Guix-patches via
2022-09-10  6:14 ` [bug#57702] [PATCH 3/8] gnu: rust-crossbeam-utils-0.8: Add development inputs VesselWave via Guix-patches via
2022-09-10  6:15 ` [bug#57702] [PATCH 4/8] gnu: rust-parking-lot-core: Inrerit from latest VesselWave via Guix-patches via
2022-09-10  6:16 ` [bug#57702] [PATCH 5/8] gnu: rust-once-cell-1: Update to 1.13.1 VesselWave via Guix-patches via
2022-09-10  6:17 ` [bug#57702] [PATCH 6/8] gnu: Add rust-clap-lex-0.2 VesselWave via Guix-patches via
2022-09-10  6:17 ` [bug#57702] [PATCH 7/8] gnu: rust-clap-derive-3: Update to 3.2.17 VesselWave via Guix-patches via
2022-09-10  6:19 ` [bug#57702] [PATCH 8/8] gnu: rust-clap-3: " VesselWave via Guix-patches via
2022-09-10  8:52 ` [bug#57702] [PATCH 1/8] gnu: Add rust-nic-emoji-char-0.9 VesselWave via Guix-patches via
2022-09-10  9:38 ` [bug#57702] [PATCH v4 " VesselWave via Guix-patches via
2022-09-11 11:37   ` Maxime Devos
2022-09-12 21:00 ` [bug#57702] [PATCH 1/8] gnu: rust-termion: Update to 1.5.6 VesselWave via Guix-patches via
2022-09-13  9:14 ` [bug#57702] [PATCH 0/8] Update rust-clap-3 to 3.2.17 VesselWave via Guix-patches via
2022-09-13  9:15 ` [bug#57702] [PATCH 1/8] gnu: rust-termion-1: Update to 1.5.6 VesselWave via Guix-patches via
2022-09-13  9:18 ` [bug#57702] [PATCH 2/8] gnu: rust-textwrap: Add 0.15.0 VesselWave via Guix-patches via
2022-09-13  9:19 ` [bug#57702] [PATCH 3/8] gnu: rust-crossbeam-utils-0.8: Add development inputs VesselWave via Guix-patches via
2022-09-13  9:19 ` [bug#57702] [PATCH 4/8] gnu: rust-parking-lot-core: Inrerit from latest VesselWave via Guix-patches via
2022-09-13  9:20 ` [bug#57702] [PATCH 5/8] gnu: rust-once-cell-1: Update to 1.13.1 VesselWave via Guix-patches via
2022-09-13  9:20 ` [bug#57702] [PATCH 6/8] gnu: Add rust-clap-lex-0.2 VesselWave via Guix-patches via
2022-09-13  9:22 ` [bug#57702] [PATCH 7/8] gnu: rust-clap-derive-3: Update to 3.2.17 VesselWave via Guix-patches via
2022-09-13  9:22 ` [bug#57702] [PATCH 8/8] gnu: rust-clap-3: " VesselWave via Guix-patches via
2022-09-20 19:31 ` John Kehayias via Guix-patches via [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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878rmd6dxn.fsf@protonmail.com \
    --to=guix-patches@gnu.org \
    --cc=57702@debbugs.gnu.org \
    --cc=VesselWave@protonmail.com \
    --cc=john.kehayias@protonmail.com \
    --cc=maximedevos@telenet.be \
    --cc=mhw@netris.org \
    --cc=paren@disroot.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).