Repository navigation
make performs a download #5705
Description
Activity
Please note that you can avoid that if you already have a (compatible) locally installed rust compiler. Check the --local-rust and --local-rust-root parameters for ./configure.
Also, I'm against bundling binaries in source tarballs. They are target-dependent and bundling all of them will make the released archive quite large.Downloading an external bootstrapper is a minor issue for downstream packagers too, though. See https://github.com/mozilla/rust/wiki/Note-packaging
far-future
Yeah, you can also just populate the
dl/directory in your builddir with an appropriate snapshot tarball. There's not much else we can do here. Putting binaries in a source tarball feels even worse, to me. Closing as I don't expect we're going to much change the requirements here and have several workable workarounds.
When you download the 0.6 tarball and execute ./configure && make, a download occurs.
and a wget info dump appears.
It would be really awesome if this piece was integrated with the tarball. Not all environments are friendly to downloading arbitrary code off the net. E.g., I might be in a SCIF[1] and experimenting with Rust on a machine disconnected from the public net. Or I might be on a laptop working in a no-wifi area. :-/
(I know this is probably a real low priority issue, but it IS a (usually minor) hassle)
[1] https://en.wikipedia.org/wiki/Sensitive_Compartmented_Information_Facility