From: "Ludovic Courtès" <ludo@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 51845@debbugs.gnu.org
Subject: [bug#51845] [PATCH 0/2] Add librsvg-bootstrap
Date: Mon, 06 Dec 2021 17:37:12 +0100 [thread overview]
Message-ID: <87wnkhlmfb.fsf@gnu.org> (raw)
In-Reply-To: <Ya4KyruleTGdYU7o@3900XT> (Efraim Flashner's message of "Mon, 6 Dec 2021 15:06:18 +0200")
Hi Efraim,
Efraim Flashner <efraim@flashner.co.il> skribis:
> On a small tangent, the work I do sometimes to try to actually have a
> dependency graph with the crates would only make these easier to find,
> not actually address the issue here.
>
> I'm not sure if it'd be better to mostly copy the packages with a new
> name and keep the cargo-inputs or to actually adjust the
> cargo-inputs->inputs and cargo-development-inputs->native-inputs so we
> get the dependency graph from rust-libc-0.2.101 to librsvg. I'd like to
> make the change but if we don't get the others changed then we
> effectively really have two sets of rust crates.
>
> If we have both cargo-inputs and inputs then the cargo-build-system
> doesn't have issues with using either type with later packages, so that
> might be the best option for now.
Thinking out loud… would it work to change:
(arguments '(#:cargo-inputs X #:cargo-development-inputs Y))
to:
(native-inputs (map package-source Y))
(inputs (map package-source X))
?
Or am I just saying nonsense?
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-12-06 16:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 14:07 [bug#51845] [PATCH 0/2] Add librsvg-bootstrap Efraim Flashner
2021-11-14 14:14 ` [bug#51845] [PATCH 1/2] gnu: " Efraim Flashner
2021-11-14 14:14 ` [bug#51845] [PATCH 2/2] gnu: Use librsvg-bootstrap Efraim Flashner
2021-11-14 17:27 ` [bug#51845] [PATCH 0/2] Add librsvg-bootstrap Liliana Marie Prikler
2021-11-14 18:07 ` Efraim Flashner
2021-11-14 19:05 ` Liliana Marie Prikler
2021-12-06 12:17 ` Ludovic Courtès
2021-12-06 13:06 ` Efraim Flashner
2021-12-06 16:37 ` Ludovic Courtès [this message]
2021-12-06 17:02 ` Efraim Flashner
2021-12-06 22:17 ` [bug#51845] Using ‘native-inputs’ and ‘inputs’ for Cargo packages? Ludovic Courtès
2021-12-07 10:11 ` Efraim Flashner
2021-12-07 19:48 ` Ludovic Courtès
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=87wnkhlmfb.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=51845@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
/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).