<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><blockquote type="cite" class=""><i class=""><font color="#000000" class="">Nils Breunese <nils at <a href="http://breun.nl" class="">breun.nl</a>> wrote:</font></i><div class=""> <br class="">It’s really too bad that even a lot of modern build tools do not have the concept of proxyable, cachable) repositories for dependencies. For instance for builds that use Maven repositories (Maven, Gradle and some other build tools in the Java ecosystem) you can set up your own proxy which fetches dependencies when first requested from upstream, stores them for future use and lets you control HTTPS settings, availability, etc. This all works because dependencies are not identified by a full URL. I believe NPM repositories will let you do the same thing for the JavaScript ecosystem.</div></blockquote><div class=""><div class=""><span class=""><br class=""></span></div><div class="">Does anyone know whether Swift Package Manager supports an offline cache, similar to Cargo’s ‘—offline’ option? That would allow us to take a point-in-time snapshot of the download/dependency cache, and reuse it for reproducible builds.</div></div><div class=""><br class=""></div><div class="">Thoughts?</div></div></body></html>