[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: rust (build system) deficits
From: |
John Soo |
Subject: |
Re: rust (build system) deficits |
Date: |
Sun, 8 Mar 2020 13:10:45 -0700 |
Hi Hartmut,
> On Mar 8, 2020, at 10:16 AM, Hartmut Goebel <address@hidden> 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
- rust (build system) deficits, Hartmut Goebel, 2020/03/07
- Re: rust (build system) deficits, John Soo, 2020/03/07
- Re: rust (build system) deficits, Hartmut Goebel, 2020/03/08
- Re: rust (build system) deficits,
John Soo <=
- Re: rust (build system) deficits, John Soo, 2020/03/08
- Re: rust (build system) deficits, Hartmut Goebel, 2020/03/09
- Re: rust (build system) deficits, Efraim Flashner, 2020/03/09
- Re: rust (build system) deficits, John Soo, 2020/03/09
- Re: rust (build system) deficits, Hartmut Goebel, 2020/03/09
- Re: rust (build system) deficits, John Soo, 2020/03/09
- Re: rust (build system) deficits, Hartmut Goebel, 2020/03/11