> On 18 Mar 2016, at 23:07, Max Howell via swift-build-dev
> <[email protected]> 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
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
