On Tuesday February 10 2015 14:42:49 Jeremy Lavergne wrote: >> Not sure you can make extended ACLs propagate the right way. > >The old school option is creating a common group for both users and have >appropriate umasks.
Yep. That's subject to the same conditions I enumerated in my previous email. If group read or write permissions aren't set in a source archive (or by tclsh) it doesn't help much. I do try to keep /opt/local in the admin group, with write access for group, though. > >However, if you're the admin user sudo is already available. I don't know about you, but I 1) don't like to have to type the same word everytime and 2) don't want to become used to prefixing every command with sudo, because one day I'm going to edit a previous command to do something "somewhere dangerous" and wipe out stuff. It happens I do a `rm -rf ./*` in a MacPorts working directory. I'd hate to repeat that command when I happen to be (say) somewhere under /System and forget there's a sudo before it... R. _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
