Document release tarballs with vendor directories filled.
andrewchambers opened this issue · comments
It has come to my attention there doesn't seem to be a way to download rust release tarballs which have dependencies vendored and submodules cloned.
The stable link here: https://forge.rust-lang.org/infra/other-installation-methods.html gives a 404 error.
The github release tarballs don't have dependencies bundled.
I'm going to move this over to forge as per my note here we do actually publish these, we're just apparently not documenting it anywhere, and we should do that.
@Mark-Simulacrum ah, I see the link. I'm slightly concerned this ticket will just be ignored similar to other forge tickets on the same topic.
see #215
@Mark-Simulacrum Note the links you provided don't have vendor directories and submodules filled.
Hm, that looks false to me? Unpacking https://static.rust-lang.org/dist/2019-08-15/rustc-1.37.0-src.tar.xz I see a vendor directory with all the crates.io deps and a quick ls src/llvm-project implies that the submodule is there as well -- can you clarify what sources you were expecting to see?
Ah thank you, I tried a rust-src link not a rustc-src link. Slightly confusing, I imagined rust would be less specific than rustc.
@Mark-Simulacrum Note the tarball you linked is not in the manifests you linked, and there is not public index so nobody has any way to find that.
Yes, we don't include it in the manifests today -- I think that's probably "just a bug" -- we'd want to be careful to not add it as a rustup component if we do add it to manifests, though.
This looks like this functionality would be easy to the mdbook plugin, however I don't know what the expected content to put in "Other Installation Methods". Which tarballs of which toolchains should be shown? What do we say about what the intended purpose of them is?
Offline builds/Distributions/package maintainers/other
@andrewchambers Distributions & Package maintainers I believe are not in the manifest files.
Sorry, I misread your question.
I'm not really clear what this issue is asking for. It looks like the links at https://forge.rust-lang.org/infra/other-installation-methods.html#source-code contain direct links to the source tarballs with all the vendoring and submodules. Since this is quite old, I'm going to assume that is now resolved.