Patrick Freed

The root user may still want to install packages just for themselves, so I don't know if we want to gate this behavior on that. However, I think it does...

Whoops, yes thanks for catching this. #69 was the one meant to be closed.

`SWIFTLY_BIN_DIR`, `SWIFTLY_HOME_DIR`, and `SWIFTLY_HOME_DIR/toolchains` are all created by each command before it runs if they don't exist, see here: https://github.com/patrickfreed/swiftly/blob/main/Sources/Swiftly/Swiftly.swift#L47. Can you share the error you were seeing / steps...

Yeah I think that's probably the best path. Today, what will happen is if you run `swiftly install `, it'll just print "\ does not exist, exiting", but for older...

Hey, yeah I think this is a cool idea. Before we decide on an implementation path, I'd like to know a bit more about how custom toolchains are typically installed...

Hey, sorry for the late response on this. Our usage of `AsyncHTTPClient` could definitely be replaced with `URLSession`, there's no technical requirement for it. I opted to use it in...

Yeah we should definitely be consistent with this. Merging `swiftly-install.sh` into swiftly itself will help with that too, we just need to make sure to use the same `promptForConfirmation` everywhere...

@dfawley [mentioned](https://github.com/grpc/grpc-go/issues/4862#issuecomment-942725634) there was an effort to create a cross-language design for this functionality, are there any updates on that?

> gRFC without implementation resources doesn't seem all that helpful. Maybe just externalize the internal doc (copy the contents to your personal account and share it)? That lets people determine...

I think it would still be valuable if the internal doc were released publicly, since it's possible the community could help brainstorm ideas for a solution that accommodates the xDS...