<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Sep 4, 2015 at 10:06 PM, Gideon Simpson <span dir="ltr"><<a href="mailto:gideon.simpson@gmail.com" target="_blank">gideon.simpson@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="margin:0px">gideon@gs_air:swig$ sudo port install</div><div style="margin:0px">Password:</div><div style="margin:0px">Error: Unable to execute port: Could not open file: /Users/gideon/Downloads/ports/swig/Portfile</div><span class="HOEnZb"><font color="#888888"><div></div></font></span></blockquote></div><br>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.</div><div class="gmail_extra"><br></div><div class="gmail_extra">MacPorts does not perform all operations as root, but drops to the unprivileged "macports" user for most things.<br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div><div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div></div>
</div></div>