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 <[email protected]> wrote: > 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 breaking changes >> in libraries seem less >> common and breaking than breaking changes in, say, plugins, so IMO we >> should stick to Cargo.lock for >> pinning and use `mach update-cargo -a` during rust upgrades. >> > > My previous message was about breaking changes in a library on crates.io, > not in the standard library. > > Many crates follow Rust master. In the past, that meant that that any > given version a library only worked with a narrow range of Rust > version/commits. As a consequence, we mostly only updated Servo’s > dependencies while doing Rust upgrades at the same time. > > But with 1.0 out this is less and less the case: many libraries can be > updated without updating Rust, and a smaller number of libraries need to be > updated when we update Rust. In time, there’ll be no reason to do both at > the same time. > > -- > Simon Sapin > _______________________________________________ dev-servo mailing list [email protected] https://lists.mozilla.org/listinfo/dev-servo
