From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: John Soo <jsoo1@asu.edu>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: rust (build system) deficits
Date: Sun, 8 Mar 2020 18:16:25 +0100 [thread overview]
Message-ID: <c487b9b1-b40f-8849-990b-4148b17215ee@crazy-compilers.com> (raw)
In-Reply-To: <543D2B96-0DD4-4274-BAF4-1761897DF812@asu.edu>
Hi John,
> My proposal is to:
> * move cargo-{development-}inputs into inputs, requiring only the source from libraries.
> * either:
> - move the rust closure function so all packages use it
> Or
> - adjust the transitive closure function such that it works on normal inputs rather than arguments
> * Do not build rust packages by default. Only run tests.
> * as a corollary to the previous item: Default skip-build? to #f but do run tests even if skip-build is #f and tests? is #t
Actually I do not care so much about cargo-{development-}inputs fields.
The much more serious issue is that we are not able to build non-trivial
Rust applications: Given a package which needs to add phases, e.g. for
fixing Cargo.toml, we would need to run each package's phases when
building any depending package.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next prev parent reply other threads:[~2020-03-08 17:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 13:46 rust (build system) deficits Hartmut Goebel
2020-03-07 18:41 ` John Soo
2020-03-08 17:16 ` Hartmut Goebel [this message]
2020-03-08 20:10 ` John Soo
2020-03-08 20:20 ` John Soo
2020-03-09 9:26 ` Hartmut Goebel
2020-03-09 11:17 ` Efraim Flashner
2020-03-09 14:00 ` John Soo
2020-03-09 14:50 ` Hartmut Goebel
2020-03-09 17:48 ` John Soo
2020-03-11 17:55 ` Hartmut Goebel
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c487b9b1-b40f-8849-990b-4148b17215ee@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=guix-devel@gnu.org \
--cc=jsoo1@asu.edu \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.