Yeah, I keep mine under ~/Development/bunch-more-dirs and it works fine. Also, my terminal has full disk access. I'm not sure if that's required or even wise, but works for me.
—Mark On Thu, Oct 30, 2025, at 12:13 PM, Joshua Root wrote: > On 31/10/2025 01:52, Chris Jones wrote: > > > > It doesn't even need to be a separate volume or shared area, its enough > > to not have it *directly* in your home area. There have been problems > > with this previously, years back (I forget the detail) but is why I keep > > mine in '~/Projects/MacPorts/ports', I have for years now, and I have > > had no issues with the current base release with that area. > Good point, Apple does use much more restrictive permissions for the > automatically created subdirectories like Documents in user home dirs. > The permissions on subdirs you create yourself will depend on your > umask. We've seen cases where the home directory itself lacked search > permissions for other users, but that's likely something the user did > rather than the default state. > > And yeah, I'm pretty sure the way macOS looks up group membership > changed at some point, because I remember the current (2.11.6) MacPorts > behaviour also happening years ago. > > - Josh > —Mark Macports Wiki Page <https://trac.macports.org/wiki/mark> | GitHub <https://github.com/markemer> | Blog <https://emer.net>
