<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 30, 2016 at 1:01 AM, Max Howell <span dir="ltr"><<a href="mailto:max.howell@apple.com" target="_blank">max.howell@apple.com</a>></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 style="word-wrap:break-word"><div><span class=""><blockquote type="cite"><div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><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 style="word-wrap:break-word"><div>1) You have to remember to modify it back at some point, and if you are iterating frequently this is tedious and error-prone</div></div></blockquote><div><br></div><div>One way I can think of to avoid Package.swift is to place DevPackages inside some special folder (perhaps: DevPackages/) inside the root package which sounds good if I am developing some patch to some package but it might be awkward if I am starting to write a library and want to create a package to try it because I'll already have created the library package (though maybe minimal) but then I'll have to move the library inside DevPackages/</div></div></div></div></div></blockquote><div><br></div></span>Well, it seems to me part of the utility here is having a package be a local clone in an entirely different directory. So this sounds a bit tedious.<span class=""><br><br></span></div></div></blockquote><div><br></div><div>Any other way you can think of to avoid Package.swift?</div><div> </div><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 style="word-wrap:break-word"><div><span class=""><blockquote type="cite"><div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>This would be a bit awkward but sounds good enough to me</div><div> <br></div><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 style="word-wrap:break-word"><div>2) We don’t want any chance that DevPackage gets into the package graph and thus the ecosystem.</div></div></blockquote><div><br></div><div>what if one of the dependencies depend on a package inside DevPackage then should the DevPackage be preferred?</div></div>
</div></div>
</div></blockquote></span></div><br><div>Don’t understand.</div></div></blockquote></div><br>RootPackage </div><div class="gmail_extra">Dependency: APackage</div><div class="gmail_extra">DevPackage: BPackage</div><div class="gmail_extra"><br></div><div class="gmail_extra">APackage</div><div class="gmail_extra">Dependency: BPackage<br><br>If DevPackages don't specify version in Package.swift, in case of a collision should the DevPackage be always preferred?<br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Ankit<br><br></div>
</div></div>