tracemode complains about $CCACHE_DIR

[afb@…]

Warning: A creation/deletion/modification was attempted outside sandbox: /Users/afb/.ccache/stats
Warning: A creation/deletion/modification was attempted outside sandbox: /Users/afb/.ccache/stats
Warning: A creation/deletion/modification was attempted outside sandbox: /Users/afb/.ccache/stats

It should ignore directories $CCACHE_DIR" and "$HOME/.ccache" (the default value of it)

[afb@…]

macports-ccachetrace.patch

[eridius@…]

I've never heard of this .ccache dir before. You sure this isn't a bug with the particular Portfile you were trying to install?

[eridius@…]

Ok, after some research I'm guessing you have the ccache port installed and that's being used? In that case, I don't think we should support it. If you want to use the ccache port, trace mode won't work for you, and that should just be a fact of life. We really shouldn't hack around this sort of thing. Maybe you can set an env var that changes the ccache dir to live in somewhere like /tmp?

[afb@…]

I don't have the ccache port, I have it installed system-wide. But I can work around it. :-P

[afb@…]

Pretty please ?

Might be more interesting to have ccache support now, when ccache is supported in MacPorts ?

See ticket #5390

[raimue@…]

I added another patch which disables filters in trace mode completely. Maybe this is a better solution?

[raimue@…]

I am revisiting this issue to find a solution eventually. I updated the patch submitted by afb for current trunk.

But another problem still exists that tracemode complains about access to the ccache binary.

trace: access denied to /opt/local/bin/ccache (ccache)

Therefore we still can't use ccache in tracemode even with this patch. What would be an appropriate solution here? Should we add ccache and distcc to some sort of whitelist (does that exist?) when they are enabled by port itself?