Discussion of the System pitch as well as pondering over my latest endeavors raises the question: while Swift is distributed officially as a large binary package with the standard library, compiler, all libraries with all the tooling trimmings, this may not be an idiomatic means of distributions on other platforms, so where do the dividing lines lie?
One might expect to have a libraries package distinct from the compiler, so that someone interested in a Swift application can install the libraries but not the compiler, but a Swift developer might expect the toolchain to have Testing (or System) without having to explicitly install it.
I know this discussion has happened before. Were any conclusions reached? Does this actually matter, or should platform packagers just use best judgement on this?
I don't think there was a formal conclusion establishing a single required package split. The general guidance seems to be that platform packagers can use their best judgement.
There was an earlier discussion that broke the Swift distribution into the toolchain, Swift-based development tools, compile-time dependencies, and runtime dependencies, which seems like a useful model for distro packaging.
The recent System discussion also reinforces that some libraries make more sense as part of the toolchain because their APIs/types need to stay version-aligned with Swift itself.
So I'd probably treat the existing Debian/Ubuntu and Termux packaging as examples rather than a strict standard, and choose the split that fits the conventions and dependency model of the target distribution.