From: Nicolas Graves via Guix-patches via <guix-patches@gnu.org>
To: "(" <paren@disroot.org>, 57231@debbugs.gnu.org
Subject: [bug#57231] [PATCH 1/3] gnu: rust-cargo-0.53: Move to (gnu packages crates-io).
Date: Sun, 21 Aug 2022 00:57:27 +0200 [thread overview]
Message-ID: <87wnb2le08.fsf@ngraves.fr> (raw)
In-Reply-To: <CM7M636EJ4HR.122F05PORAU0C@guix-aspire>
On 2022-08-16 18:03, ( wrote:
> Huh? I don't think rust-cargo is actually an "app"
I don't believe so, it pulls from the same crate detailed as the real
one on crates.io (https://crates.io/crates/cargo).
There might be some duplicate code here. I don't see source code in
my rust:cargo store folder, but I believe this should be the same code,
making this package unnecessary (with some work we could add rust:cargo
in inputs for rust-cargo-c, since it's the only place it's used in).
Can't delve in this next week however.
--
Best regards,
Nicolas Graves
next prev parent reply other threads:[~2022-08-20 23:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 21:08 [bug#57231] Fix rust-cargo build Nicolas Graves via Guix-patches via
2022-08-15 21:14 ` [bug#57231] [PATCH 1/3] gnu: rust-cargo-0.53: Move to (gnu packages crates-io) Nicolas Graves via Guix-patches via
2022-08-15 21:14 ` [bug#57231] [PATCH 2/3] gnu: rust-cargo-0.53: Rename package to rust-cargo Nicolas Graves via Guix-patches via
2022-08-15 21:14 ` [bug#57231] [PATCH 3/3] gnu: rust-cargo: Repare build phase Nicolas Graves via Guix-patches via
2022-08-16 17:03 ` [bug#57231] [PATCH 1/3] gnu: rust-cargo-0.53: Move to (gnu packages crates-io) ( via Guix-patches via
2022-08-20 22:57 ` Nicolas Graves via Guix-patches via [this message]
[not found] ` <87bkqy1h4y.fsf@ngraves.fr>
2022-09-29 13:04 ` bug#57231: " Nicolas Graves via Guix-patches via
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=87wnb2le08.fsf@ngraves.fr \
--to=guix-patches@gnu.org \
--cc=57231@debbugs.gnu.org \
--cc=ngraves@ngraves.fr \
--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).