Quick dependancy is not correctly versioned about siesta

[pcantrell]

This is now released as Siesta 1.5.2, so you should be able to update your Package.swift accordingly. Let me know if you hit any troubles!

FWIW, it looks like Swift 5.3.1 includes the further SwiftPM enhancements above, so now SwiftPM shouldn’t even download Quick and Nimble for downstream projects that don’t need them.

[pcantrell]

Great news! I’ll try to get a point release out with this fix soon.

There’s one more SwiftPM improvement related to this issue that they’ve merged but not yet released, and if I understand correctly, it should stop downstream projects from fetching Quick and Nimble at all.

[caipre]

Looks like it is indeed working, thanks @pcantrell !

[omidontop]

Thank you Paul! Great work!!

[caipre]

I'm running into the same basic issue after adding Quick and Nimble to my own project. Swift Package Manager is unable to resolve dependencies because Siesta uses https://github.com/pcantrell/Quick instead of https://github.com/Quick/Quick . It was surprising to me that this was a problem since these are test dependencies, but it seems Swift PM makes no such distinction.

My workaround is to use the same forked version of Quick and pin to 0.0.0 as Siesta is doing. This is less than ideal though, since the fork will always lag behind upstream.

[pcantrell]

Could one (or both) of you switch your dependency on Siesta to the bump-swift-package-version branch, and see if that fixes your problem?

(Your client shouldn’t pick up Quick/Nimble at all, and SwiftPM has actively been working on resolving this. Their recent work may fix it if Siesta’s Package.swift specifies the newer behavior.)

[omidontop]

Could one (or both) of you switch your dependency on Siesta to the bump-swift-package-version branch, and see if that fixes your problem?

(Your client shouldn’t pick up Quick/Nimble at all, and SwiftPM has actively been working on resolving this. Their recent work may fix it if Siesta’s Package.swift specifies the newer behavior.)

Hi Paul!

It did resolve the issue indeed! It still retrieves Quick and Nimble but doesn't complain anymore. Thank you for your help and dedication! When do you think it can be merged and released?

[omidontop]

Great news! I’ll try to get a point release out with this fix soon.

There’s one more SwiftPM improvement related to this issue that they’ve merged but not yet released, and if I understand correctly, it should stop downstream projects from fetching Quick and Nimble at all.

Excellent! Then perhaps that issue would be solved in the next Swift version too. Thank you so much!