On Feb 4, 2025, at 06:38, Gregorio Litenstein wrote: > > I've been running my entire macports environmen on an external drive. I make > this work almost seamlessly by having it listed in /etc/fstab and set to > mount at /opt.
You will want to do something similar for /Applications/MacPorts For a time I ran our Apple Silicon buildbot worker that way (because we want case-sensitive volumes on our buildbot and it was not possible at the time for us to reformat the main volume case-sensitive) and it worked fine. I have considered enhancing our GitHub Actions setup to do this as well, since we cannot influence the case sensitivity of the main volume of their runners. Note that nothing prevents ports from installing files to yet other locations. However most ports do confine themselves to those two locations. > sometimes, I can't eject the disk cleanly because secd (invoked by the > macports user) is has the keychain at > `/opt/local/var/macports/home/Library/Keychains/` permanently open. Of > course, I can kill that instance of secd (My usual workaround) but I was > wondering, a) What is on that keychain, and b) Whether it might be possible > to change something in the way macports talks to secd so this doesn't happen? I am not aware of the existence of that keychain nor of any functionality in MacPorts that uses keychain.
