From: "Ludovic Courtès" <ludo@gnu.org>
To: Martin Becze <mjbecze@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: Overhauling the cargo-build-system
Date: Sat, 16 Nov 2019 22:33:32 +0100 [thread overview]
Message-ID: <87imnjtsk3.fsf@gnu.org> (raw)
In-Reply-To: <e2b9941a46d4d552652732d6d5f14be0@riseup.net> (Martin Becze's message of "Fri, 15 Nov 2019 22:31:34 -0800")
Hello!
Martin Becze <mjbecze@riseup.net> skribis:
> Sorry for digging up and old issue, but i just saw commit
> 86e443c71d4d19e6f80cad9ca15b9c3a301c738c
>
>> It makes for a very large package definition, but we
> wouldn't have to ensure thousands of other rust libraries built so we
>
> The whole point of package management is that you can use module
> building blocks. By having to specify the sub-dependencies in a top
> level definition kinda breaks the whole modular thing. In commit
> 86e443c71d4d19e6f80cad9ca15b9c3a301c738c all the inputs got removed for
> all the libraries. So if I'm trying to use guix as package manager for a
> rust project and I want to use one of the rust libraries in
> crates-io.scm, how am i suppose to do this? I can't just include it as
> an input to my project because now I have to look up all of it
> dependencies as well?
I agree that removing all the dependencies from Rust packages feels
wrong.
What I would have liked is to somehow replace the #:cargo-inputs
argument (which is build-system-specific and thus “opaque”) with regular
‘native-inputs’ or ‘inputs’ field.
I know it’s not that easy with Rust and Cargo, I just never manage to
fully grasp why :-), but at least that should be our horizon IMO.
WDYT, Efraim, Martin, and other Rusty people? :-)
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-11-16 21:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 15:50 Overhauling the cargo-build-system Efraim Flashner
2019-10-10 22:33 ` Ludovic Courtès
2019-10-11 14:13 ` Efraim Flashner
2019-11-16 6:31 ` Martin Becze
2019-11-16 16:37 ` John Soo
2019-11-16 18:44 ` Martin Becze
2019-11-16 21:33 ` Ludovic Courtès [this message]
2019-11-17 2:35 ` Martin Becze
2019-11-17 7:19 ` Efraim Flashner
2019-11-17 21:22 ` Ludovic Courtès
2019-11-18 10:20 ` Efraim Flashner
2019-11-23 17:27 ` Ludovic Courtès
2019-12-09 4:45 ` Chris Marusich
2019-12-09 20:14 ` Martin Becze
2019-12-19 16:10 ` Ludovic Courtès
2019-12-19 16:09 ` Ludovic Courtès
2019-12-19 17:23 ` John Soo
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=87imnjtsk3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mjbecze@riseup.net \
/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).