The following still doesn’t work: gideon@gs_air:swig$ chmod o+x ~ gideon@gs_air:swig$ sudo port install Error: Unable to execute port: Could not open file: /Users/gideon/Downloads/ports/swig/Portfile
-gideon > On Sep 4, 2015, at 10:17 PM, Brandon Allbery <[email protected]> wrote: > > On Fri, Sep 4, 2015 at 10:06 PM, Gideon Simpson <[email protected] > <mailto:[email protected]>> wrote: > gideon@gs_air:swig$ sudo port install > Password: > Error: Unable to execute port: Could not open file: > /Users/gideon/Downloads/ports/swig/Portfile > > Make sure that the user "macports" can get to that directory. This usually > means "chmod o+x ~" to grant search (only) privilege so that it can traverse > ~ to get to the swig subdirectory. (If you are feeling paranoid, you can use > "chmod -e" to limit that access to the "macports" user instead of all users; > see `man 1 chmod` for how OS X ACLs work.) Likewise ensure that the swig > directory grants access to the "macports" user and that that user can read > the Portfile and patch. > > MacPorts does not perform all operations as root, but drops to the > unprivileged "macports" user for most things. > > -- > brandon s allbery kf8nh sine nomine associates > [email protected] <mailto:[email protected]> > [email protected] <mailto:[email protected]> > unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net > <http://sinenomine.net/>
_______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
