On Jan 19, 2020, at 17:47, Dave Allured wrote:
> Is there an easy way to get macports to go through the motions of "port
> install -s" for a single port, using macports infrastructure, and taking port
> dependencies from /opt/local, but writing only inside a user directory? This
> would only be for testing that port's build process, not for actually
> installing into the real port tree. My now-hypothetical case is a package
> that fails parallel build under macports, but never fails when parallel
> building externally, with only autotools. I would like to find what the
> differences are, to help make a simpler reproducer.
It used to be that if you did not use "sudo", then "port install ..." would
write into ~/.macports instead of /opt/local/var/macports. I don't know if
that's still the case. I did not appear to work when I tried it just now but
maybe I have something configured differently.
