From mboxrd@z Thu Jan 1 00:00:00 1970 From: Martin Becze Subject: Re: Overhauling the cargo-build-system Date: Sat, 16 Nov 2019 10:44:12 -0800 Message-ID: <2797a314493ce274b83ea93459ade815@riseup.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:43395) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iW33V-00063I-9T for guix-devel@gnu.org; Sat, 16 Nov 2019 13:44:22 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iW33R-00062d-An for guix-devel@gnu.org; Sat, 16 Nov 2019 13:44:21 -0500 In-Reply-To: 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: John Soo Cc: guix-devel@gnu.org, Guix-devel > It is quite frustrating to have to specify transitive dependencies at > the top level. I=E2=80=99m not sure what else is to be done, though. How about having something like "propagated-input" for rust source dependencies? The top level package could use the source deps as development-inputs so the source files wouldn't end up polluting the environment. Would that make sense?