From: John Soo <jsoo1@asu.edu>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: rust (build system) deficits
Date: Sun, 8 Mar 2020 13:10:45 -0700 [thread overview]
Message-ID: <4F4B169B-8A25-440C-8A29-DC39DC94814F@asu.edu> (raw)
In-Reply-To: <c487b9b1-b40f-8849-990b-4148b17215ee@crazy-compilers.com>
Hi Hartmut,
> On Mar 8, 2020, at 10:16 AM, Hartmut Goebel <h.goebel@crazy-compilers.com> wrote:
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.
Hmm. Can you elaborate more on “not able to build non-trivial rust applications”? It seems like we have finally made some progress on building some rust apps. Patching a library Cargo.toml seems like an excellent job for source patches or snippets. Modifying an executable’s Cargo.toml to refer to guix-vendor happens during a phase that matters (because the executable will be built).
We also already have solutions for removing censored code for c library wrappers.
Clearly the situation is not ideal, but I do think there are improvements to take just with what we have now.
Kindly,
John
next prev parent reply other threads:[~2020-03-08 20:10 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
2020-03-08 20:10 ` John Soo [this message]
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=4F4B169B-8A25-440C-8A29-DC39DC94814F@asu.edu \
--to=jsoo1@asu.edu \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.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 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.