<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="">Though it’s not the default, you can actually tell MacPorts to use Git to sync your ports, at least; see the third part of <a href="https://guide.macports.org/#installing.macports.git" class="">section 2.3.3 in the guide</a>.<div class=""><br class=""><div class="">
Saagar Jha
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On Jun 5, 2020, at 16:05, Christopher Chavez <<a href="mailto:chrischavez@gmx.us" class="">chrischavez@gmx.us</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On 6/5/2020 12:32 PM, Clemens Lang wrote:<br class=""><blockquote type="cite" class="">or switch to a different source, e.g. git<br class=""></blockquote>As a user, I've thought it would be great if MacPorts used git syncing<br class="">by default. I have used git-over-https since 2016 when I was constrained<br class="">to ports 80/443 by a university campus network. I had found it also<br class="">avoided needlessly writing hundreds of MB to the SSD when updating the<br class="">ports tree. If GitHub outages are a concern, then I would think falling<br class="">back to a mirror hosted by GitLab/SourceForge/Bitbucket/etc. should be<br class="">possible.<br class=""><br class="">Christopher A. Chavez<br class=""></div></div></blockquote></div><br class=""></div></body></html>