<div dir="ltr"><br><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">This was more or less what I’ve been thinking, but lately I’ve been also thinking it would be great if:<div><br></div><div>You didn’t have to modify Package.swift to get this feature.</div><div><br></div><div>Because:</div><div><br></div><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><br></div><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>