Daniel Silverstone

I'm not sure if we have any control over the server's SSL support since it's cloudfront/AWS I think. @pietroalbini Do you know about this? Even if we do support it,...

Oh interesting, that's useful to know. I assume similar exists for RHEL given their close connection to each other then.

I am still aware of companies still using RHEL 6 with direct support from Redhat, so I'd prefer not to disable this just yet.

Realistically this stems from https://github.com/rust-lang/rustup/blob/master/src/toolchain.rs#L620-L633 which currently only supports a single fallback path for cargo. If, instead, we created a unique fallback path for this toolchain, and then cleaned up...

Unfortunately I don't have a good suggestion. Perhaps someone else who does a lot of work with linked toolchains on Windows might be able to suggest something.

What would you expect `rustup` to do in this situation? simply give you no output?

Okay, so this is partially plausible. The issue I have is that `rustup {target,component} {add,remove}` are impotent on custom/linked toolchains, thus having `list` be magical might be confusing for some...

We've recently been putting in work which actually makes this harder (but makes it better in the codebase) perhaps we could make it warn if it's not a dist toolchain...

@cramertj My current thoughts on custom toolchains is that they tend to be used primarily by compiler/stdlib devs and as such don't need component support. **Instead** we need to make...

I did start to write up a starter-for-ten on how custom toolchain providers might present channels and how Rustup might consume them coherently - https://hackmd.io/X_xhHKHnRnycDDJURv2M4A?view - it is still a...