From mboxrd@z Thu Jan  1 00:00:00 1970
From: Danny Milosavljevic <dannym@scratchpost.org>
Subject: Re: cargo-build-system: cargo-build-flags: --cfg=unix in package
	recipe
Date: Tue, 3 Jan 2017 21:10:50 +0100
Message-ID: <20170103211050.16ddba55@scratchpost.org>
References: <20170103021018.64ac3887@scratchpost.org>
	<20170103033234.7d3573ec@scratchpost.org>
	<CAL1_imniTUJzG1ApQ7WoqGAp9tU7SWfBKowE8p68iSQwaUEQwQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:54548)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <dannym@scratchpost.org>) id 1cOVQD-0008Vg-BQ
	for guix-devel@gnu.org; Tue, 03 Jan 2017 15:11:02 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <dannym@scratchpost.org>) id 1cOVQA-0004mR-7N
	for guix-devel@gnu.org; Tue, 03 Jan 2017 15:11:01 -0500
Received: from dd1012.kasserver.com ([85.13.128.8]:34563)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <dannym@scratchpost.org>)
	id 1cOVQA-0004mC-1T
	for guix-devel@gnu.org; Tue, 03 Jan 2017 15:10:58 -0500
In-Reply-To: <CAL1_imniTUJzG1ApQ7WoqGAp9tU7SWfBKowE8p68iSQwaUEQwQ@mail.gmail.com>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: David Craven <david@craven.ch>
Cc: guix-devel <guix-devel@gnu.org>

Hi David,

On Tue, 3 Jan 2017 11:57:48 +0100
David Craven <david@craven.ch> wrote:

> > Aha! It can - if one uses propagated-inputs in the package recipes. I think the importer should propagate inputs if the current package is Rust-source-only. Otherwise packages further down the dependency graph (further to the clients) won't compile later.  
> 
> One of the ideas behind the [replace] stuff in the Cargo.toml file was
> to retain the required dependencies.

Just to be sure, I mean if it's two hops away.

If rust-a requires rust-b and rust-b requires rust-libc, then rust-a won't find rust-libc. Maybe it doesn't directly use it but since compilation of rust-a will also compile (compile!) rust-b, that compilation needs rust-libc but can't find it. Not sure how "replace" would have helped this specific situation...