<div dir="ltr">I think even the source URL will also work on tags </div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 15, 2015 at 1:33 PM, Kostiantyn Koval <span dir="ltr"><<a href="mailto:konstantin.koval1@gmail.com" target="_blank">konstantin.koval1@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>There is a plan to add ability to support fetching packages by url for development purpose described here</div><div>Importing Dependencies by Source URL form "PackageManagerCommunityProposal" </div><div><a href="https://github.com/apple/swift-package-manager/blob/master/Documentation/PackageManagerCommunityProposal.md#importing-dependencies-by-source-url" target="_blank">https://github.com/apple/swift-package-manager/blob/master/Documentation/PackageManagerCommunityProposal.md#importing-dependencies-by-source-url</a></div><div><span class="HOEnZb"><font color="#888888"><div><div><div><br></div><div>Kostiantyn</div></div>
</div></font></span><div><div class="h5">
<br><div><blockquote type="cite"><div>On 14 Dec 2015, at 22:36, Kostiantyn Koval <<a href="mailto:konstantin.koval1@gmail.com" target="_blank">konstantin.koval1@gmail.com</a>> wrote:</div><br><div><div style="word-wrap:break-word"><div>+1 for adding this.</div><div><br></div>Ability to point to commit instead of a tag is crucial. <div>Often happens that a bug was fixed in the depended library but it wasn't released/tagged.</div><div>As well it helps during development.</div><div><br></div><div><div><div><div><div>Kostiantyn</div></div>
</div>
<br><div><blockquote type="cite"><div>On 14 Dec 2015, at 20:14, Marc Knaup via swift-build-dev <<a href="mailto:swift-build-dev@swift.org" target="_blank">swift-build-dev@swift.org</a>> wrote:</div><br><div><p dir="ltr" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">+1 since I had to do exactly that a couple of times with CocoaPods.<br>There were issue in third party Pods which were fixed in a specific commit or branch but the official release would still take a while. Delaying our app release because of that was not an option and referring to a fixed yet unreleased version the best solution.<span> </span></p><div class="gmail_quote" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">On Dec 14, 2015 8:04 PM, "Ankit Agarwal via swift-build-dev" <<a href="mailto:swift-build-dev@swift.org" target="_blank">swift-build-dev@swift.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>Correcting one of the sentences in the Detailed design section</div><div><br></div><div>* If pointed to a branch, there might be two broad use cases</div><div>1. User wants to point a branch due to active development of that dep and wants latest ref available in that branch</div><div>2. User is actively developing a dep in that branch and want to test it out in the current package</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 15, 2015 at 12:13 AM, Ankit Agarwal<span> </span><span dir="ltr"><<a href="mailto:ankit@ankit.im" target="_blank">ankit@ankit.im</a>></span><span> </span>wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><br></div><div>Hi,</div><div><br></div><div>Here is a proposal of the adding git branch support feature in SPM</div><div><br></div><div><b>Introduction</b></div><div><br></div><div>Pointing to branch or a commit ref for dependencies in Package.swift as opposed to only a tagged release.</div><div><br></div><div><b>Motivation</b></div><div><br></div><div>* Try a package which is almost stable or useable but not yet ready for a release/pre-release so not tagged (eg: new feature being introduced by a library)</div><div>* While developing packages, one would want to point a package that uses the package to a develop branch (eg: Developing Foo package, Bar uses Foo and wants to point Foo dep to develop branch)</div><div>* One would want to point to his own fork but not create a release while developing/testing (eg: Fork a library not compatible with SPM to make it compatible)</div><div>* One wants to point to some commit but doesn't have a branch/tag created for that</div><div><br></div><div><b>Proposed solution</b></div><div><br></div><div>Allow refs and branch in Package.swift</div><div><br></div><div>let package = Package(</div><div> <span> </span>name: "Hello",</div><div> <span> </span>dependencies: [</div><div> <span> </span>.Package(url: "ssh://<a href="http://git@example.com/Greeter.git" target="_blank">git@example.com/Greeter.git</a>", branch: "develop", shouldFastForward: true),</div><div> <span> </span>.Package(url: "ssh://<a href="http://git@example.com/FooBar.git" target="_blank">git@example.com/FooBar.git</a>", commit: "d8ec7ca398a3ac3990477028117384d05ca7734e"),</div><div> <span> </span>]</div><div>)</div><div><br></div><div><b>Detailed design</b></div><div><br></div><div>* Only the root Package.swift would be able to use branch/ref feature to avoid dependency hell, any other dependency fetched in current Package should not compile if that dependency contains another dependency pointing to a branch/ref</div><div>* This feature should strictly be used for testing/developing purpose and should not be deployed to production environments</div><div><br></div><div>SPM could have the following behavior when running `swift build` :</div><div><br></div><div>* If pointed to a branch, there might be two use cases </div><div>Since there is a high probability that user wants to point a branch due to active development of that dep and wants latest ref available in that branch</div><div>If a dependency is not cloned, clone it and checkout that branch</div><div>If shouldFastForward is on -> Always try to be on the latest ref, disregard any local changes made to the checked out package</div><div>If shouldFastForward is false -> Always try to be on the latest ref unless any local changes made to the checked out package</div><div><br></div><div>* If pointed to a ref : </div><div>If that dependency is not cloned, clone it and checkout that ref.</div><div>Consecutive `swift build` will not affect the cloned package</div><div>If changes are made in the cloned repo, rebuild that package with those changes</div><div><br></div><div><b>Impact on existing code</b></div><div><br></div><div>None as this will be a new functionality</div><div><br></div><div><b>Alternatives considered</b></div><div><br></div><div>One option is to only allow a commit ref and not a branch so SPM will not have to worry about fast forwarding but this is a desired feature.</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 8, 2015 at 4:24 AM, Rick Ballard<span> </span><span dir="ltr"><<a href="mailto:rballard@apple.com" target="_blank">rballard@apple.com</a>></span><span> </span>wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span>> On Dec 5, 2015, at 5:59 AM, Ankit Agarwal <<a href="mailto:ankit@ankit.im" target="_blank">ankit@ankit.im</a>> wrote:<br>><br>> Hi,<br>><br>> Is pointing to a branch instead of version for a package in scope of SPM?<br>> if it is, I'd love to try to implement it<br><br></span>Hi Ankit,<br><br>This is in scope, though not yet designed. Prior to anyone working on an implementation, we should agree on a design for how you'd do this. While this isn't at the top of our priority list at the moment, we'd welcome both design contributions and eventual implementation.<br><br>If you'd like to put a proposal together for this, please see the Swift evolution process at<span> </span><a href="https://github.com/apple/swift-evolution/blob/master/process.md" rel="noreferrer" target="_blank">https://github.com/apple/swift-evolution/blob/master/process.md</a>. We'd be happy to discuss this here as part of your process for putting a proposal together. Some things to think about in this area are:<br><br>– How should refs (branches or tags) that aren't simple version numbers be specified?<br><br>– Right now we require you to tag something as a versioned "release". Should we require that you tag a branch before someone can make a package depend on it? It could be convenient to be able to just depend on a branch, but the meaning of depending on a branch changes over time as more commits come in. Is it harmful to allow packages to depend on something that's not an identified commit?<br><br> <span> </span>– Note that we have yet to design our security story (<a href="https://github.com/apple/swift-package-manager/blob/master/Documentation/PackageManagerCommunityProposal.md#security-and-signing" rel="noreferrer" target="_blank">https://github.com/apple/swift-package-manager/blob/master/Documentation/PackageManagerCommunityProposal.md#security-and-signing</a>); what we settle on there might require dependencies to be specified as a specific tagged commit, so that it can be signed.<br><br>– Should it be possible to override a package's dependency to use a different branch, without having to modify and commit a change to that package's Package.swift?<br><br>– We may want to design a way for packages to support different versions of the Swift language, as the language continues to change – e.g. a branch of the package for the last released swift vs the current under development swift snapshot. Is supporting dependencies on package branches a part of how we'll do that?<br><br>Thanks,<br><br> <span> </span>- Rick<br><br><span><font color="#888888"></font></span></blockquote></div><span><font color="#888888"><br><br clear="all"><div><br></div>--<span> </span><br><div>Ankit<br><br></div></font></span></div></div></blockquote></div><br><br clear="all"><div><br></div>--<span> </span><br><div>Ankit<br><br></div></div><img src="https://u2002410.ct.sendgrid.net/wf/open?upn=6ZGE61OxINd5lLe2xYh9Ku-2BXbixWNr2nvfzp2IB1sZitVEVOLMb3PkOgG1oZLriinC-2FhjxzCJITVIxLERxmQg9GykePbiPlZ-2B6zOplZh-2BPGWS-2BgsCVN3Gu5wBtRYUFte73OobYkI8ehlI2z5kWfJRDEEI6SdysmehMyAnR3lsQ16729oOKy-2FUKXtBMRU5ITlM8QMd-2Fn-2Fi47oO2o1t7dhfG7SaMCEoAD7K1rzQQnU2Js-3D" alt="" width="1" height="1" border="0" style="min-height:1px!important;width:1px!important;border-width:0px!important;margin:0px!important;padding:0px!important"><span> </span><br>_______________________________________________<br>swift-build-dev mailing list<br><a href="mailto:swift-build-dev@swift.org" target="_blank">swift-build-dev@swift.org</a><br><a href="https://lists.swift.org/mailman/listinfo/swift-build-dev" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-build-dev</a><br><br></blockquote></div><img src="https://u2002410.ct.sendgrid.net/wf/open?upn=n3jPUXkT5YFxadHQEoaOww8U5ADISS-2FbZlg0rksvZj78wabIoZVrI-2FgONKOZ7HZugOnFJCUauHc2MU6Fiofd-2BtS9Lxq4mTyiXjcTLjyIZBXTLahqTlU3WlQfewKvoBu3pEZ0x6-2BpmPgPf6bcemqi3ZRi-2BgiXfU4dtVUT-2FdceRVxq1A0Si09YAAWXMu3NKKM5CbFrvYBu-2BBlqzUt0Ob-2FmLVmrTqGkqPPvimCHrscYiTo-3D" alt="" width="1" height="1" border="0" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;min-height:1px!important;width:1px!important;border-width:0px!important;margin:0px!important;padding:0px!important"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important"><span> </span>_______________________________________________</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">swift-build-dev mailing list</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><a href="mailto:swift-build-dev@swift.org" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank">swift-build-dev@swift.org</a><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><a href="https://lists.swift.org/mailman/listinfo/swift-build-dev" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank">https://lists.swift.org/mailman/listinfo/swift-build-dev</a></div></blockquote></div><br></div></div></div></div></blockquote></div><br></div></div></div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Ankit<br><br></div>
</div>