unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Nicolas Graves <ngraves@ngraves.fr>
Cc: Felix Lechner <felix.lechner@lease-up.com>,
	 Vagrant Cascadian <vagrant@debian.org>,
	 Maxime Devos <maximedevos@telenet.be>,
	guix-devel@gnu.org
Subject: Re: rust-build-system from antioxidant
Date: Fri, 16 Jun 2023 20:51:00 -0400	[thread overview]
Message-ID: <87zg4yud1n.fsf@gmail.com> (raw)
In-Reply-To: <87352ra4zg.fsf@ngraves.fr> (Nicolas Graves's message of "Fri, 16 Jun 2023 15:53:07 +0200")

Hi Nicolas,

Nicolas Graves <ngraves@ngraves.fr> writes:

> Hi all,
>
> Thanks for this discussion that I didn't expected to happen ;)
>
> I'll try and finish a version of the rust-build-system but I'd like to
> know if there are reasons to not want a direct and complete rewrite of
> all Rust packages before putting more time into this. My rationale is
> that since we have channels, users won't really be affected in any
> meaningful way because adding a "snapshot of cargo packages" in a
> channel and then adding the channel is straightforward.

Thank you!

My impression is that the Rust packaging in Guix is so problematic that
if a way would mean less work for you and motivate you to push this work
to the finish line it, that may well be the better way :-).

> I've merged the rust-build-system and rust-workspace-build-system into a
> single one, and made some UX improvements (a dozen patches on top of
> Maxime's work).
>
> If atomicity / readability of changes is the issue, I can try to cut the
> packages rewrites into patches (although that would make more than 1k
> patches total I think).

That would match our convention better, if it's not too difficult to
accomplish (is this going to be automated?  I've written some imperfect
but useful automatic rewriting tool in the past to remove the Python 2
packages [0].  Perhaps it could provide some ideas)

[0]  https://notabug.org/apteryx/guix-api-examples/src/master/purge-python2-packages.scm

-- 
Thanks,
Maxim


      reply	other threads:[~2023-06-17  0:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02 18:02 rust-build-system from antioxidant Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2023-06-08 17:55 ` Maxime Devos
2023-06-12  1:17   ` Maxim Cournoyer
2023-06-12 10:10     ` Maxime Devos
2023-06-12 13:05       ` Maxim Cournoyer
2023-06-14 13:02         ` Maxime Devos
2023-07-02 20:12       ` Overruling and blocking Ludovic Courtès
2023-06-12 15:08     ` rust-build-system from antioxidant Vagrant Cascadian
2023-06-12 16:34       ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-06-16 13:53         ` Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2023-06-17  0:51           ` Maxim Cournoyer [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=87zg4yud1n.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=felix.lechner@lease-up.com \
    --cc=guix-devel@gnu.org \
    --cc=maximedevos@telenet.be \
    --cc=ngraves@ngraves.fr \
    --cc=vagrant@debian.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).