Restrict platforms for packages?

SDGGiesbrecht · October 2, 2019, 1:00am

I have no opinion of my own, but I can provide a few links If you are curious about the history of the API for specifying platforms.

Here is the proposal that added platform specification:

github.com

apple/swift-evolution/blob/main/proposals/0236-package-manager-platform-deployment-settings.md

# Package Manager Platform Deployment Settings

* Proposal: [SE-0236](0236-package-manager-platform-deployment-settings.md)
* Authors: [Ankit Aggarwal](https://github.com/aciidb0mb3r)
* Review Manager: [Boris Bügling](https://github.com/neonichu)
* Status: **Implemented (Swift 5)**
* Decision Notes: [Rationale](https://forums.swift.org/t/accepted-with-modifications-se-0236-package-manager-platform-deployment-settings/18420)
* Previous Revisions: [1](https://github.com/apple/swift-evolution/blob/aebb22c0f3e139fd921d14f79c3945af99d0342d/proposals/0236-package-manager-platform-deployment-settings.md)

## Introduction

This is a proposal for adding support for specifying a per-platform minimum required deployment target in the `Package.swift` manifest file.

## Motivation

Packages should be able to declare the minimum required platform deployment target version. SwiftPM currently uses a hardcoded value for the macOS deployment target. This creates friction for packages which want to use APIs that were introduced after the hardcoded deployment target version.

There are two ways to work around this limitation: 1) using availability checks, or 2) passing the deployment target on the command line while building the package. However, these workarounds are not ideal and the package manager should really provide a proper API for setting the required deployment target version.

## Proposed solution

This file has been truncated. show original

Here is its review:

And here is its acceptance: