Re: rust: cargo build-system: how to handle libraries

[ng0 <ng0@libertad.pw>]

ng0 <ng0@libertad.pw> writes:

> David Craven <david@craven.ch> 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