Description
If you are following the SwiftPM PR feed, you'll have seen the team rushing in updates to the SwiftVersion global to match the release of the toolchain for the given branch. That's a very cumbersome process and it actually doesn't imply a version of SwiftPM itself.
We should reconsider what it is to be a SwiftPM version. As you see with the swift-driver version, it's a combination of things. One of them is the version of swift-driver that's in the same toolchain as SwiftPM. We are using the swiftCompilerTag in a number of places to customize behaviour based on the Swift compiler version, e.g. selection of prebuilts and in the future Swift SDKs. And we have SwiftPM's ToolsVersion which actually enables and disables features of SwiftPM and that is based on the major and minor version of the toolchain that SwiftPM is targeted for.
Interesting things happen when we are working on SwiftPM outside of the toolchain and are working against a recent release or snapshot of another toolchain. Showing all these version components would be helpful at identifying the combination. Question is, do we need a patch level for the SwiftPM version? Or is the patch level from the toolchain SwiftPM is embedded in sufficient?
Expected behavior
No response
Actual behavior
No response
Steps to reproduce
No response
Swift Package Manager version/commit hash
No response
Swift & OS version (output of swift --version && uname -a)
No response
Description
If you are following the SwiftPM PR feed, you'll have seen the team rushing in updates to the SwiftVersion global to match the release of the toolchain for the given branch. That's a very cumbersome process and it actually doesn't imply a version of SwiftPM itself.
We should reconsider what it is to be a SwiftPM version. As you see with the swift-driver version, it's a combination of things. One of them is the version of swift-driver that's in the same toolchain as SwiftPM. We are using the swiftCompilerTag in a number of places to customize behaviour based on the Swift compiler version, e.g. selection of prebuilts and in the future Swift SDKs. And we have SwiftPM's ToolsVersion which actually enables and disables features of SwiftPM and that is based on the major and minor version of the toolchain that SwiftPM is targeted for.
Interesting things happen when we are working on SwiftPM outside of the toolchain and are working against a recent release or snapshot of another toolchain. Showing all these version components would be helpful at identifying the combination. Question is, do we need a patch level for the SwiftPM version? Or is the patch level from the toolchain SwiftPM is embedded in sufficient?
Expected behavior
No response
Actual behavior
No response
Steps to reproduce
No response
Swift Package Manager version/commit hash
No response
Swift & OS version (output of
swift --version && uname -a)No response