Support for specifying a branch for a dependency. #236
Conversation
|
I don't know if this is desirable....have you looked at the ongoing lockfile proposal which aims to solve problems like this? |
|
This will be solved with Lock file. Please have a look at Lock proposal draft. |
|
Most package managers seems to have a feature like this. I needed it myself to use the Swift 3.0 branch of a library. |
|
Under current proposal once you add a dependency, you can go into that package and git checkout the branch you want to use and "lock" it in order to propagate the changed branch to other users of your package. |
) This reverts commit 17e8e68 because the `insert()` is actually rewriting the array for every single discovered dependency. This can cause a significant performance hit. See <rdar://problem/38225211>
In a Package dependency, you can now specify an optional branch, and this branch will get cloned when getting dependencies.
It currently defaults to "master" if not specified (and will use 'git clone -b master').
Currently the branch will not influence the package name, but the name and tag should be enough that it doesn't conflict.