[swift-build-dev] How to use the Package.pins file

Steven Clukey saclukey at live.com
Tue Dec 20 08:13:11 CST 2016

> Loose specifications allow libraries to avoid unnecessarily causing dependency conflicts for one another. 

I agree, and SE-0145 specifically recommends against using pinning for libraries.

> The "pins" file allows application builds to reliably produce the same resolution, time after time.

If an application requires the exact same dependency version resolution, then why not put an exact version in the manifest? What is the point, or the benefit, of using a loose version in the application's manifest plus an exact version in the "pins" file instead of just using an exact version in the manifest to begin with?


More information about the swift-build-dev mailing list