From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Craven Subject: Re: rust work in progress conflicts Date: Fri, 29 Jul 2016 11:46:31 +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]:45606) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bT4NM-0008B1-2O for guix-devel@gnu.org; Fri, 29 Jul 2016 05:46:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bT4NH-0002Jf-66 for guix-devel@gnu.org; Fri, 29 Jul 2016 05:46:40 -0400 Received: from mail-yw0-x229.google.com ([2607:f8b0:4002:c05::229]:34432) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bT4NF-0002ID-VR for guix-devel@gnu.org; Fri, 29 Jul 2016 05:46:35 -0400 Received: by mail-yw0-x229.google.com with SMTP id z8so110419453ywa.1 for ; Fri, 29 Jul 2016 02:46:32 -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 Hi Eric! Nice! 1. Try using 'guix environment --ad-hoc gcc gcc:lib'. 2. I thought about this. Maybe we could add a cargo subcommand that interacts with the guix/nix daemon directly [0] and then have a small cargo-build-system that wraps it. I think this would be neat because we could avoid repackaging all rust crates and nixos could maybe reuse it too. Otherwise we are rewriting a lot of stuff that cargo already does really well (not like python and ruby package managers for example) [0] https://github.com/rust-lang/cargo/wiki/Third-party-cargo-subcommands