Re: [dev-servo] (Not) using wildcard version when declaring dependencies

2015-06-15 Thread Manish Goregaokar
Yes, I was talking about Crates crates too :) My plan is to upgrade Rust often now that it's pretty stable, which automatically keeps our libraries up to date too. But if we don't want to do that I guess pinning to semver is okay. -Manish Goregaokar On Tue, Jun 16, 2015 at 2:52 AM, Simon Sapin

Re: [dev-servo] (Not) using wildcard version when declaring dependencies

2015-06-15 Thread Simon Sapin
On 15/06/15 23:03, Manish Goregaokar wrote: From what I've seen, semver isn't being used to it's full extent yet, especially with libraries working on nightly. Locking to particular versions tends to make rustups harder (and leads to multiple versions of the same package being used). The breakin

Re: [dev-servo] (Not) using wildcard version when declaring dependencies

2015-06-15 Thread Manish Goregaokar
From what I've seen, semver isn't being used to it's full extent yet, especially with libraries working on nightly. Locking to particular versions tends to make rustups harder (and leads to multiple versions of the same package being used). The breaking changes in libraries seem less common and bre

[dev-servo] (Not) using wildcard version when declaring dependencies

2015-06-15 Thread Simon Sapin
Some of our dependencies to crates on crates.io are declared in Cargo.toml files like this: [dependencies] foo = "*" To be honest, I’m not sure why. With such a declaration, `cargo update` will happily update the foo library to its latest version, whatever it is. There’s a number of things w