Ports tree setup for development
bruce.johnson289 at gmail.com
Sat Sep 8 09:10:53 UTC 2018
That worked well. Thanks, Chris.
Seems port selfupdate tries to recursively set the ownership of the
# set the MacPorts sources to the right owner
set sources_owner [file attributes [file join $portdbpath sources/]
ui_debug "Setting MacPorts sources ownership to $sources_owner"
exec [macports::findBinary chown $macports::autoconf::chown_path]
-R $sources_owner [file join $portdbpath sources/]
As for the git slowness. I figured it out. I have some code that runs a
number of git calls each time my prompt is generated, in order to display
information about (un)staged changes etc., and since the repo is so large,
it was just taking a while to run these commands.
On Thu, Sep 6, 2018 at 9:09 PM Christopher Jones <jonesc at hep.phy.cam.ac.uk>
> I have a complete clone of the port tree, but just under my regular user
> Oberon ~/Projects/MacPorts/ports > git status
> On branch master
> Your branch is up to date with 'origin/master'.
> nothing to commit, working tree clean
> then, in your macports sources.conf, just point it at this area as your
> new default.
> > tail -4 /opt/local/etc/macports/sources.conf
> # If an rsync URL points to a .tar file, a signed .rmd160 must exist next
> # it on the server and will be used to verify its integrity.
> #rsync://rsync.macports.org/release/tarballs/ports.tar [default]
> file:///Users/chris/Projects/MacPorts/ports [default]
> thats it. everything is automatic after that. ‘sudo port sync’ updates
> that area, as your regular user.
> 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.
> On 6 Sep 2018, at 8:31 pm, Bruce Johnson <bruce.johnson289 at gmail.com>
> Just wondering how people have their ports tree set up for development?
> I ask because I had cloned the macports-ports repo to:
> 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 :-)
> 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.
> Would be good to hear how others are setup and whether you have any tips.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the macports-dev