~/.macports

[Brandon Allbery]

On Tue, Feb 10, 2015 at 9:30 AM, René J.V. <rjvbertin at gmail.com> wrote:

> On Tuesday February 10 2015, Brandon Allbery wrote regarding "Re:
> ~/.macports"
> >Not supported, not a great idea, not an outright installation-breaking
> >idea. (Among other potential problems, a Portfile bug could nuke your home
> >directory; with a dedicates macports user, it would get a permission
> error.)
>
> True, but that kind of bugs are unlikely to appear in released ports, or
> so I'd hope. In any case I've never yet had this happen to me.
>

I think someone did have this (try to) happen to them recently-ish. I also
know people who had a Homebrew installation eat itself, because it does
everything as the logged-in user.

I strongly prefer safety in things like this.


> I take it there is no official way to define the permissions mask for a
> macports user that would allow an admin user full control over content
> owned by the macports user (but not the reverse)?


Not sure you can make extended ACLs propagate the right way.

-- 
brandon s allbery kf8nh                               sine nomine associates
allbery.b at gmail.com                                  ballbery at sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20150210/56f3a26c/attachment.html>