[swift-evolution] [Review] SE-0145: Package Manager Version Pinning

Martin Waitz tali at admingilde.org
Thu Nov 3 01:17:40 CDT 2016


> Am 03.11.2016 um 03:22 schrieb Daniel Duan <daniel at duan.org>:
> On Nov 2, 2016, at 3:46 PM, Martin Waitz via swift-evolution <swift-evolution at swift.org> wrote:
> 
>>> What is your evaluation of the proposal?
>> 
>> +1 for using reproducible versions of dependencies
>> -1 for the actual proposal
>> 
>> My problem with this proposal is that it tries to please everybody by introducing options everywhere.
>>>> We should just drop all these problems and design a system which works for all use-cases
>> without having to manually pin dependencies.
> 
> The second half of the sentence contradicts with the first half. What if I need to only pin some of the dependencies, have have the rest update automatically?

No contradiction:
Storing versions of all dependencies and having reproducible builds is independent from updating dependencies.
What you need is some automatic (e.g. driven by CI) system to update your dependencies.

When performing an update is the right time to select what you want to update.
Then you can also test the new set and document that you chose to update them.

Updates should always be explicit actions, not happening randomly at checkout time.

— Martin


More information about the swift-evolution mailing list