[swift-build-dev] Proposal: Git Branch and ref support for dependencies in Swift Package Manager
eloy.de.enige at gmail.com
Tue Dec 22 15:17:41 CST 2015
In addition, people like to unlock specific dependencies and their implicit dependencies. E.g.:
1. Install dependencies as per the lockfile: $ swift build
2. Unlock all dependencies: $ swift build —update
3. Unlock specific dependency and its implicit dependencies: $ swift build —update [Dependency Name]
> On 22 Dec 2015, at 20:53, orta therox via swift-build-dev <swift-build-dev at swift.org> wrote:
> This behaviour is consistent with every dependency manager I’ve used, and really should be the way SPM works. If you build, it bases it off the lockfile, if you specifically decide to update, then you should say so.
> [A.] Orta Therox
>> w/ Artsy <http://artsy.net/>CocoaPods <http://cocoapods.org/> / CocoaDocs <http://cocoadocs.org/> / GIFs.app <https://itunes.apple.com/us/app/gifs/id961850017?l=en&mt=12>
>> @orta <http://twitter.com/orta> / orta.github.com <http://orta.github.com/>
>> Artsy is totally hiring iOS Devs <https://artsy.net/job/mobile-engineer> ATM
>> On 22 Dec 2015, at 18:47, Max Howell via swift-build-dev <swift-build-dev at swift.org <mailto:swift-build-dev at swift.org>> wrote:
>> If the lock file is committed I think swift-build should always use it. If the user wants newer updates they can execute `swift build —update`.
> swift-build-dev mailing list
> swift-build-dev at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-build-dev