Could you specify that in the tag of the dependency you need? >= 3.0.0   vs   = 
2.0.0  etc... I am not sure why in some cases we need to be unique over state 
of the art like Cocoapods in some areas. What is the added value (not saying 
that there is none)?

Sent from my iPhone

> On 3 Nov 2016, at 02:22, Daniel Duan via swift-evolution 
> <[email protected]> wrote:
> 
> On Nov 2, 2016, at 3:46 PM, Martin Waitz via swift-evolution 
> <[email protected]> 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?
> 
> 
> _______________________________________________
> swift-evolution mailing list
> [email protected]
> https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution

Reply via email to