From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: rust: cargo build-system: how to handle libraries Date: Wed, 28 Dec 2016 16:49:06 +0000 Message-ID: <87zijg3sot.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> References: <8760m5c4dv.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> <87eg0ss8xl.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> <87bmvws8tf.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> <87pokcgg3a.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50123) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cMHPN-0005dH-Us for guix-devel@gnu.org; Wed, 28 Dec 2016 11:48:58 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cMHPK-0003yX-Pr for guix-devel@gnu.org; Wed, 28 Dec 2016 11:48:57 -0500 Received: from aibo.runbox.com ([91.220.196.211]:44636) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cMHPK-0003yH-If for guix-devel@gnu.org; Wed, 28 Dec 2016 11:48:54 -0500 In-Reply-To: <87pokcgg3a.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> 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: David Craven Cc: guix-devel@gnu.org ng0 writes: > David Craven writes: > >>> Of course I meant Cargo.lock, not Cargo.toml ... so I know what I >>> have to search for, and this makes it a bit easier than the >>> previous search. >> >> See cargo workspaces: >> https://github.com/rust-lang/libc/blob/master/Cargo.toml >> https://github.com/rust-lang/rfcs/blob/master/text/1525-cargo-workspace.md > > Aha! Thanks :) > >> It's a fairly new thing, you'll have to track down the relevant >> commits in cargo and check if the cargo version we are using is new >> enough and understand it's semantics and how it applies to the cargo >> build system. > > Is the cargo version attached to the rustc version? In other > words, could I try and package cargo 0.15 (released 6 days ago) > and it will not care about the rustc version? Okay, I understand how we (currently) package rust and cargo, I try to upgrade rust to 1.14, maybe this helps. >> My recommendation to fix this issue is to not run the tests if there >> isn't a Cargo.lock file, but this is likely not going to solve the >> underlying cause in this case. You can also package version 0.2.16 >> which does not use workspaces. > > Are there mechanisms in place in either (our) cargo build-system > or cargo in general to disable tests, or do I have to write this > (if I would run into problems with packaging 0.15 cargo)? > > -- > ♥Ⓐ ng0 > PGP keys and more: https://n0is.noblogs.org/ http://ng0.chaosnet.org -- ♥Ⓐ ng0 PGP keys and more: https://n0is.noblogs.org/ http://ng0.chaosnet.org