From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: David Craven <david@craven.ch>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Rust
Date: Wed, 7 Sep 2016 08:04:56 +0200 [thread overview]
Message-ID: <20160907080456.3e11ff6a@itchy> (raw)
In-Reply-To: <CAL1_imk7uV=NZVj+_qiwZpMb2_sVXkjNS=oDEajYv8T07jM+EQ@mail.gmail.com>
Hi!
Le Sun, 4 Sep 2016 16:50:48 +0200,
David Craven <david@craven.ch> a écrit :
> > IIUC, to provide a Guix package for Cargo, the following should be
> > done:
>
> > 1. write a crate importer.
> > 2. list all the crates needed by Cargo to build itself.
> > 3. package each crate with the importer.
> > 4. add a Cargo package which depends on the newly-imported crates
> > and uses a binary version of Cargo to bootstrap itself (though this
> > is not the best option in terms of auditing/reproducibility).
>
> Have you made any progress on this? =)
Unfortunately no. Bandwith is a little bit low ATM :-(
I sent an updated version of the Rust package, taking into account the
suggestions from the original version.
> FYI I also think that that's the best course of action. I remember
> dealing with non gnu-build-system packages in nixos was a bit of a
> pain, so I was biased against the importer thing. I think guix does a
> better job at it...
>
> To build the crates needed to build cargo a good idea is probably to
> have rust-build-system take a #:cargo and a #:rustc package. Then you
> can pass the binary versions for bootstrapping cargo.
Thanks for the suggestion.
Best regards,
--
ELB
next prev parent reply other threads:[~2016-09-07 6:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-04 14:50 Rust David Craven
2016-09-07 6:04 ` Eric Le Bihan [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-07-29 19:10 Rust David Craven
2016-07-30 13:39 ` Rust Ludovic Courtès
2016-03-25 17:45 LLVM: "FileCheck" is missing Danny Milosavljevic
2016-03-25 22:06 ` rust work in progress conflicts (was: Re: LLVM: "FileCheck" is missing) Nils Gillmann
2016-05-04 10:34 ` Jelle Licht
2016-05-05 15:06 ` rust work in progress conflicts ng0
2016-07-28 8:28 ` ng0
2016-07-28 18:31 ` Eric Le Bihan
2016-07-29 15:16 ` Rust Ludovic Courtès
2016-07-29 15:34 ` Rust Alex Griffin
2016-07-29 16:08 ` Rust Jelle Licht
2016-07-30 13:34 ` Rust Ludovic Courtès
2016-07-30 17:57 ` Rust Pjotr Prins
2016-07-30 11:01 ` Rust Eric Le Bihan
2016-07-30 13:44 ` Rust 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=20160907080456.3e11ff6a@itchy \
--to=eric.le.bihan.dev@free.fr \
--cc=david@craven.ch \
--cc=guix-devel@gnu.org \
/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).