From: Jason Conroy <jconroy@tscripta.net>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: rust-team branch merged
Date: Wed, 24 Apr 2024 11:58:22 -0400 [thread overview]
Message-ID: <WFQNCB7USY4L3WPQY9RV5ETTORRP4QD5HTX074ZZ2OJSX0TNB0@tscripta.net> (raw)
In-Reply-To: <Zikns2W615nNz52q@pbp>
Efraim Flashner <efraim@flashner.co.il> writes:
> On the other hand, by generating it during the build of each
> package we
> make sure to pull in all the crates which exist in the build, so
> we
> could add into a profile/manifest just the crates listed in a
> Cargo.toml
> and then each crate would pull in its own dependencies, and then
> the
> profile hook could combine them all together.
Thanks. Just to make sure I understand: it sounds like you're
saying that by creating the JSON index files up front, we'd be
preserving some knowledge about a package's dependency graph that
isn't easily recovered later by recursively walking through inputs
and cargo-inputs for the package specs in a manifest/profile?
Jason
next prev parent reply other threads:[~2024-04-24 16:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 8:34 rust-team branch merged Efraim Flashner
2023-12-13 14:02 ` Maxim Cournoyer
2023-12-14 15:10 ` Efraim Flashner
2024-02-27 2:24 ` Jason Conroy
2024-03-06 9:06 ` Efraim Flashner
2024-03-06 17:53 ` Jason Conroy
2024-03-07 8:08 ` Efraim Flashner
2024-03-07 16:48 ` Jason Conroy
2024-03-12 15:12 ` Efraim Flashner
2024-03-13 15:06 ` Jason Conroy
2024-04-18 16:54 ` Jason Conroy
2024-04-24 15:39 ` Efraim Flashner
2024-04-24 15:58 ` Jason Conroy [this message]
2024-04-24 16:23 ` Efraim Flashner
2024-05-06 14:00 ` Jason Conroy
2023-12-14 23:09 ` Csepp
-- strict thread matches above, loose matches on Subject: below --
2023-05-09 7:32 Efraim Flashner
2023-05-09 8:33 ` Christopher Baines
2023-05-09 8:54 ` Efraim Flashner
2023-05-09 9:27 ` Andreas Enge
2023-05-09 9:28 ` Andreas Enge
2023-05-09 13:22 ` Christopher Baines
2023-05-09 14:04 ` Efraim Flashner
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=WFQNCB7USY4L3WPQY9RV5ETTORRP4QD5HTX074ZZ2OJSX0TNB0@tscripta.net \
--to=jconroy@tscripta.net \
--cc=efraim@flashner.co.il \
--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 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).