14 ms·
That doesn't seem to talk about the series of "checksum ..." entries in the [metadata] section at the end of the Cargo.lock.
by dbaupp 8y ago
That doesn't seem to talk about the series of "checksum ..." entries in the [metadata] section at the end of the Cargo.lock.
- e12e 8y agoHm, appears to be an alternate (new? Old?) syntax for: "Cargo will take the latest commit and write that information out into our Cargo.lock when we build for the first time. That file will look like this: [[package]] name = "hello_world" version = "0.1.0" dependencies = [ "rand 0.1.0 (git+https://github.com/rust-lang-nursery/rand.git#9f35b8e439eeedd60b9414c58f389bdc6a3284f9)" https://github.com/rust-lang-nursery/rand.git#9f35b8e439eeed..., ] [[package]] name = "rand" version = "0.1.0" source = "git+https://github.com/rust-lang-nursery/rand.git#9f35b8e439eeedd60b9414c58f389bdc6a3284f9" https://github.com/rust-lang-nursery/rand.git#9f35b8e439eeed... You can see that there’s a lot more information here, including the exact revision we used to build."
- dbaupp 8y agoNo, the git hashes are still there in the same syntax as described in that document. In fact, the checksum entry of a git dependency seems to be "<none>".