<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="">Hi,<div class=""><br class=""></div><div class="">I have a complete clone of the port tree, but just under my regular user account.</div><div class=""><br class=""></div><div class=""><div class="">Oberon ~/Projects/MacPorts/ports > git status</div><div class="">On branch master</div><div class="">Your branch is up to date with 'origin/master'.</div><div class=""><br class=""></div><div class="">nothing to commit, working tree clean</div><div class=""><br class=""></div><div class="">then, in your macports sources.conf, just point it at this area as your new default.</div><div class=""><br class=""></div><div class=""><div class="">> tail -4 /opt/local/etc/macports/sources.conf</div><div class=""># If an rsync URL points to a .tar file, a signed .rmd160 must exist next to</div><div class=""># it on the server and will be used to verify its integrity.</div><div class="">#<a href="rsync://rsync.macports.org/release/tarballs/ports.tar" class="">rsync://rsync.macports.org/release/tarballs/ports.tar</a> [default]</div><div class=""><a href="file:///Users/chris/Projects/MacPorts/ports" class="">file:///Users/chris/Projects/MacPorts/ports</a> [default]</div></div><div class=""><br class=""></div><div class="">thats it. everything is automatic after that. ‘sudo port sync’ updates that area, as your regular user.</div><div class=""><br class=""></div><div class="">Regarding the git slowness though, no, I do not see anything like that. You are going to have to provide more details on what exactly you mean.</div><div class=""><br class=""></div><div class="">Chris</div><div class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On 6 Sep 2018, at 8:31 pm, Bruce Johnson <<a href="mailto:bruce.johnson289@gmail.com" class="">bruce.johnson289@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class="">Hi,<div class=""><br class=""></div><div class="">Just wondering how people have their ports tree set up for development?</div><div class=""><br class=""></div><div class="">I ask because I had cloned the macports-ports repo to:</div><div class=""><br class=""></div><div class=""> /opt/local/var/macports/sources/<a href="http://github.com/macports/macports-ports" class="">github.com/macports/macports-ports</a><br class=""></div><div class=""><br class=""></div><div class="">then ran `sudo port selfupdate` and all the files then changed ownership to root. D'oh! After chowning the entire ports tree back to my user, I then figured I could use `port sync` to only update the ports tree and retain ownership, which worked well :-)</div><div class=""><br class=""></div><div class="">My remaining qualm is that git interactions are quite slow, which is probably just a function of the repo size, and therefore difficult to do anything about.</div><div class=""><br class=""></div><div class="">Would be good to hear how others are setup and whether you have any tips.</div><div class=""><br class=""></div><div class="">Thanks.</div><div class=""><br class=""></div></div></div>
</div></blockquote></div><br class=""></div></body></html>