From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Craven Subject: Re: Rust Date: Sun, 4 Sep 2016 16:50:48 +0200 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43613) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bgYl6-0003IT-HC for guix-devel@gnu.org; Sun, 04 Sep 2016 10:50:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bgYl2-0001Xm-DK for guix-devel@gnu.org; Sun, 04 Sep 2016 10:50:55 -0400 Received: from mail-yw0-x22c.google.com ([2607:f8b0:4002:c05::22c]:34145) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bgYl1-0001X9-5r for guix-devel@gnu.org; Sun, 04 Sep 2016 10:50:52 -0400 Received: by mail-yw0-x22c.google.com with SMTP id g192so36854594ywh.1 for ; Sun, 04 Sep 2016 07:50:49 -0700 (PDT) List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel , eric.le.bihan.dev@free.fr > 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? =) 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.