The fix in MacPorts 2.11.6 is certainly needed, but it has indeed some inconvenient side effects when using a local Portfile sources…. I can change of course the permissions as you said earlier Josh, but then “git” wants me to commit all the Portfiles with the changed permissions.
Renee > On Oct 30, 2025, at 12:23 AM, Joshua Root <[email protected]> wrote: > > Off the top of my head I can only think of two ways to make this "just work", > and they're both bad. > > 1. Don't run as an unprivileged user > 2. Automatically mess with permissions on the user's home directory > > - Josh > > On 30/10/2025 13:55, Aaron Madlon-Kay wrote: >> Ok but this is a significant new annoyance (regression) for anyone with >> local sources. If there was a way to address this without putting the burden >> on users that would be nice. >> On Thu, Oct 30, 2025 at 11:02 Joshua Root <[email protected] >> <mailto:[email protected]>> wrote: >> On 30/10/2025 12:26, Aaron Madlon-Kay wrote: >> > I'm having the same issue locally with my local port source. Is this >> > intended given the changes to permissions handling? It seems to make >> > managing an additional, local source quite difficult. >> It has always been intended that the macports user have minimal >> privileges. That means it can't read your files unless you give it >> permission. >> > [ls of portfile] >> > -rw-r--r-- 1 aaron.madlon.kay staff 3465 Oct 30 10:12 >> > /Users/aaron.madlon.kay/Code/MacPorts/devel/gradle/Portfile >> All parent directories also need to have appropriate permissions. >> Adding >> o+x should suffice I think. That does give search permission on your >> home directory to everyone, not just macports, of course. Alternatives >> include putting the repo somewhere outside your home directory, or >> using >> ACLs. >> - Josh >
