Why was the macports user implemented

Brandon Allbery allbery.b at gmail.com
Wed Aug 31 17:16:24 PDT 2011

On Wed, Aug 31, 2011 at 15:26, Rodolfo Aramayo <raramayo at gmail.com> wrote:

> Great. Good explanation. Thanks, but then that begs the question as to
> why the files in '/opt/local/' are not owned by macports:macports and
> instead by 'root:admin and/or root:wheel'? Am I missing something in
> here??

You don't want to allow Portfiles to remove random files owned by you;
likewise, you don't want to allow it to remove random files installed by
other ports (which you have implicitly validated by "port install"ing them
as some user other than the macports user; this is normally root but might
be yourself or some other user if you chose).  The port build environment is
set up to protect not only your files but also the rest of MacPorts.
 Ideally it'd be a sandbox in which only the port's own working files could
be modified by a rogue command, but MacPorts isn't quite there yet.

brandon s allbery                                      allbery.b at gmail.com
wandering unix systems administrator (available)     (412) 475-9364 vm/sms
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20110831/3190f1d1/attachment.html>

More information about the macports-users mailing list