[swift-evolution] [swift-build-dev] Proposal Discussion Thread: SwiftPM: Locking and Overriding Dependencies

Eloy Durán eloy.de.enige at gmail.com
Fri Mar 18 18:00:04 CDT 2016

> On 18 Mar 2016, at 23:07, Max Howell via swift-build-dev <swift-build-dev at swift.org> wrote:
>> The two points above are just the low-hanging fruit that came into my mind. I prefer the approach CocoaPods takes with `Podfile.lock` being next to the repo manifest, instead of in the `Pods` folder (which instead contains a `Manifest.lock` AFAIK). So does Rubygems and others.
> Indeed, it is not conventional. I’m not committed to the location in the proposal, but I do still prefer it.

Drive-by chiming in on this.

The reason CocoaPods has two copies of the lockfile is so that the versions of the installed dependencies (Manifest.lock) can be compared to the required dependency versions (Podfile.lock). This is needed for when the dependency dir is ignored from SCM and this is why that lockfile is located inside the dependency dir.

– Eloy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160319/61d80f05/attachment.html>

More information about the swift-evolution mailing list