From: "Murilo" <murilo@disroot.org>
To: "MSavoritias" <email@msavoritias.me>, <guix-devel@gnu.org>
Subject: Re: Idea for packaging rust apps
Date: Fri, 24 May 2024 09:10:01 -0300 [thread overview]
Message-ID: <D1HV42PT7N9T.1VUWJDNXC3XUR@yumiko> (raw)
In-Reply-To: <2d322c0e-4f82-1b3d-0af8-88f8980f34a6@fannys.me>
Hi MSavoritias,
> I wanted to ask, are you also aware of the antioxidant effort?
> https://notabug.org/maximed/cargoless-rust-experiments
I was not aware of it at all, thank you for enlightening me about the
effort.
> I was wondering of the differences since your build system seems to
> still be using cargo under the hood instead of rustc.
Yes, you are correct. It really does nothing special except making
packaging of rust apps for the end user extremely easy. This approach
still uses the cargo-build-system, it is not a replacement for it,
thus carrying all the cargo (and cargo-build-system) flaws along with
it.
The antioxidant-build-system, on the other hand, aims to mainly solve
the inefficiencies of the cargo-build-system and cargo itself. After
looking at some mail exchange on the antioxidant effort, it will be
hopefully much nicer to make rust packages once the rust-build-system
is merged, and it will be a much better approach for Guix than what I
am currently suggesting.
I believe my approach with cargo2guix and transitively generating guix
package definitions from Cargo.lock will mainly target user's Guix
channels because of the simplicity of the packaging process. While it
is better than what we currently have on Guix, it is nowhere ideal for
Guix as the antioxidant effort is, because of CI and the amount of
packages Guix has.
Thank you once again for making me aware of antioxidant and the future
rust overhaul on Guix.
--
Best regards,
Murilo
prev parent reply other threads:[~2024-05-25 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 2:04 Idea for packaging rust apps Murilo
2024-05-22 12:54 ` MSavoritias
2024-05-24 12:10 ` Murilo [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=D1HV42PT7N9T.1VUWJDNXC3XUR@yumiko \
--to=murilo@disroot.org \
--cc=email@msavoritias.me \
--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.