From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Craven Subject: Re: WIP patch: build-system: cargo: Make lots and lots of rust packages work Date: Tue, 3 Jan 2017 12:08:56 +0100 Message-ID: References: <20170103024407.6928-1-dannym@scratchpost.org> <20170103025103.8147-1-dannym@scratchpost.org> <20170103050157.223af717@scratchpost.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36472) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cOMxi-0004df-2u for guix-devel@gnu.org; Tue, 03 Jan 2017 06:09:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cOMxd-0003Sc-Bn for guix-devel@gnu.org; Tue, 03 Jan 2017 06:09:02 -0500 Received: from mail-qt0-x22e.google.com ([2607:f8b0:400d:c0d::22e]:33972) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cOMxd-0003SV-6d for guix-devel@gnu.org; Tue, 03 Jan 2017 06:08:57 -0500 Received: by mail-qt0-x22e.google.com with SMTP id d45so237348694qta.1 for ; Tue, 03 Jan 2017 03:08:57 -0800 (PST) In-Reply-To: <20170103050157.223af717@scratchpost.org> 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: Danny Milosavljevic Cc: guix-devel > For it to work, you also have to back out the (cons "src" outputs) (in ./guix/build-system/cargo.scm) and the (assoc-ref outputs "src") (in guix/build/cargo-build-system.scm) starting from current master. Can you elaborate on why you think it's a bad idea to separate the source from the binaries into different outputs? I see that you are trying to mimic what cargo vendor does. Cool proof of concept and nice solution to the computing sha256 hashes on the build side. The question is if this is the best approach. I was thinking of trying [0] first and see how that works for the build system use case. The cargo package example using vendoring is intended to be a temporary solution, and I'm not sure we have finished exploring the "design space" yet. [0] https://github.com/alexcrichton/cargo-local-registry