el capitan

[Clemens Lang]

Hi,

On Wed, Jan 27, 2016 at 08:12:46PM -0600, Mark Brethen wrote:
> 1/27/16 8:07:05.232 PM sandboxd[116]: ([327]) xcodebuild(327) deny file-write-data /opt/local/var/macports/home/Library/Preferences/com.apple.dt.xcodebuild.plist

Xcode trying to modify preferences. This deny is harmless because we
never keep this preferences file anyway -- it is copied form the
executing user's ~/Library on startup.

> 1/27/16 7:54:01.522 PM sandboxd[116]: ([95150]) mdworker(95150) deny file-read-data /opt/local/share/devhelp/books/vala-0.30/default.css (import fstype:hfs fsflag:480D000 flags:5E diag:0 isXCode:0 uti:public.html plugin:/Library/Spotlight/RichText.mdimporter - find suspect file using: sudo mdutil -t 4063742)

We don't want mdworker to index any files when started from within the
build environment (which is the only environment where it would be
sandboxed by us), so this is fine.

> 1/27/16 7:11:59.062 PM sandboxd[116]: ([1526]) Python(1526) deny file-write-unlink /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/_sysconfigdata.pyc

This usually happens during the build or destroot phase (because the
install phase does have write access to this location), and we don't
want build systems to modify already installed files or system locations
in this phase, so this one is actually a good thing.

> 1/27/16 6:55:33.014 PM sandboxd[116]: ([95150]) mdworker(95150) deny file-read-data /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_vala/vala/work/vala-0.30.0/doc/vala/default.css (import fstype:hfs fsflag:480D000 flags:240000005E diag:0 isXCode:0 uti:public.html plugin:/Library/Spotlight/RichText.mdimporter - find suspect file using: sudo mdutil -t 4062840)
> 
> 1/27/16 9:27:14.350 AM sandboxd[116]: ([95150]) mdworker(95150) deny file-read-data /opt/local/share/gtk-doc/html/libxml2/left.png (import fstype:hfs fsflag:480D000 flags:5E diag:0 isXCode:0 uti:public.html plugin:/Library/Spotlight/RichText.mdimporter - find suspect file using: sudo mdutil -t 3254918)

mdworker again, see above.

-- 
Clemens