From: "Ludovic Courtès" <ludo@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: 53127@debbugs.gnu.org
Subject: bug#53127: [PATCH RFC] Turning Rust/Cargo inputs into “regular” inputs?
Date: Mon, 10 Jan 2022 09:58:35 +0100 [thread overview]
Message-ID: <87zgo4ynk4.fsf@inria.fr> (raw)
In-Reply-To: <f31aa42f47fef21dd459771402601ddbe16998a9.camel@gmail.com> (Liliana Marie Prikler's message of "Sat, 08 Jan 2022 20:47:46 +0100")
Hi!
Liliana Marie Prikler <liliana.prikler@gmail.com> skribis:
> I suppose adding (package-source rust-cargo) to inputs to preserve the
> old meaning would not make much sense?
No because you need transitivity (that is, you need sources of the
dependencies, too).
> If so, what about having a source output and using (list `(,rust-cargo
> "source") ...)?
AFAICS it wouldn’t help solve the problems I mentioned.
>> Last, the change to ‘inputs’ would introduce a few cycles at the
>> <package> level. Those cycles vanish when we lower to bags and
>> derivations. However, because of these cycles, things like ‘guix
>> refresh -l’ may not work; there might be other unexpected and
>> undesired side effects.
> What about making the change incrementally, so that outer layers can
> start adopting the new style while inner layers are being
> rebootstrapped. I also think it'd make sense to see how we could
> detect cycles through static analysis.
Yeah, we could change things incrementally if that helps.
However, given that ‘guix style’ can automate all the changes, I think
we could just as well change everything at once. The good thing is that
it allows us that the strategy we choose actually works at scale, in
every case.
>> Some of these cycles could in theory be removed. For instance,
>> ‘rust-cfg-if’ has an optional dependency on ‘rust-compiler-builtins’,
>> which leads to a cycle, but Cargo won’t let us actually remove that
>> dependency, even though it’s optional.
> Could we rewrite the toml file to tell Cargo it has no power over us?
> Could we define bootstrap mockups?
Maybe, I don’t know!
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-01-10 9:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 17:57 bug#53127: [PATCH RFC] Turning Rust/Cargo inputs into “regular” inputs? Ludovic Courtès
2022-01-08 19:47 ` Liliana Marie Prikler
2022-01-10 8:58 ` Ludovic Courtès [this message]
2022-01-10 20:24 ` Liliana Marie Prikler
2022-01-11 10:11 ` 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=87zgo4ynk4.fsf@inria.fr \
--to=ludo@gnu.org \
--cc=53127@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
/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).