macOS: Should swiftly support toolchains in /Library/Developer/Toolchains?

[iainsmith]

Some people prefer to install the toolchains to /Library/Developer/Toolchains for all users on the system to use. Do people think swiftly should support this use case through configuration / prompt / auto detecting / not for now?

Would people want to support this through a SWIFTLY_TOOLCHAINS env variable?

From swiftly init

/Users/iain/Library/Application Support/swiftly - Data and configuration files directory including toolchains
/Users/iain/Library/Application Support/swiftly/bin - Executables installation directory

Note that the locations can be changed with SWIFTLY_HOME and SWIFTLY_BIN environment variables and run
this again.

[cmcgee1024]

Swiftly is a single user-level tool, and generally avoids operating at the system level, escalating privileges to accomplish its tasks. This is why in Linux swiftly doesn't automatically install system packages for you. Instead it prints them out, or provides the command in a "post install" files that you can use to accomplish that. Installing toolchains in /Library/Developer/Toolchains requires sudo when running the installer tool.

Assuming that swiftly did install toolchains for all users of the system in some (e.g. a post-install kind of mechanism) how will those other users access swiftly? Is it just that they get access to the toolchains that one user installs for them using swiftly?