Podfile.lock For Path Dependencies

Sample project for this CocoaPods issue: CocoaPods/CocoaPods#4211

The project/pods dependency graph is:

To run it just execute build.sh:

$ ./build.sh

The bug

The Podfile.lock clearly states the dependency "AMCoreAudio (1.1)", but if you pod install, it will change the Podfile.lock to point to "AMCoreAudio (1.5)". This happens because the strict dependecy on Intermediate.podspec changed from '1.1' to '< 2'.

The bug is: if this was not a path dependency, the Podfile.lock would be respected.

Commenting this line on analyzer.rb avoids this behaviour. This way, if you need to update the Podfile.lock, you run pod update.

Meta

Created by Daniel Ribeiro

Released under the MIT License: http://www.opensource.org/licenses/mit-license.php

http://github.com/danielribeiro/Podfilelock-for-path-dependencies/