[swift-evolution] [swift-build-dev] [Review] SE-0135: Package Manager Support for Differentiating Packages by Swift version

Anders Bertelrud anders at apple.com
Thu Aug 4 16:04:15 CDT 2016

On 2016-08-04, at 08.57, Daniel Dunbar via swift-build-dev <swift-build-dev at swift.org> wrote:

> 2. This doesn't handle situations where we change the APIs within the manifest itself -- older SwiftPM versions won't be able to parse them and won't know what to do.

Also:  In discussing this, we also considered doing something like putting the version number in a comment line at the very top of the `Package.swift`, so that it could always be string-searched even in cases in which a new-format manifest isn't parseable by an older SwiftPM.

But that feels quite hacky, and we didn't want to do that if we could avoid it.  For one thing, we want to make newly created packages that support just the latest Swift not start out with a bunch of cruft in the form of specially formatted comments etc.  And secondly, well, it's just ugly.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160804/29f5e622/attachment.html>

More information about the swift-evolution mailing list