BUG: xcode-based ports fail at destroot stage because of mtree violations in base-1.5.1

[nox@…]

I've got a strange error with libsd-framework when I upgraded it on 1.5.1. I haven't experiencied it when i've tested the port yesterday, so I'm pretty sure the error came from the recent 1.5.1 selfupdate. The error was Error: Target org.macports.destroot returned: no files matched glob pattern "*" so I've enabled trace output to see where it came from and I first thought it was a mtree violation, but an xcode-based application port doesn't produce this error.

% sudo port -dt destroot libsdl-framework
<snip>
** BUILD SUCCEEDED **
DEBUG: Executing destroot_finish
DEBUG: checking for mtree violations
Warning: A creation/deletion/modification was attempted outside sandbox: /.vol/234881026/50782114/EB515BE3-65EF-419B-A7CF-0CCF1B387824-2261-000003BFB24835A7
Warning: A creation/deletion/modification was attempted outside sandbox: /.vol/234881026/50782114/Framework Without X11 Stuff (for those who didn't install the X11 headers with Xcode).dep
Error: Target org.macports.destroot returned: no files matched glob pattern "*"
Warning: the following items did not execute (for libsdl-framework): org.macports.destroot
Error: Status 1 encountered during processing.

% sudo port -dt destroot libsdl_image-framework
<snip>
** BUILD SUCCEEDED **
DEBUG: Executing destroot_finish
DEBUG: checking for mtree violations
Warning: Target destroot has an undeclared dependency on libiconv
Warning: Target destroot has an undeclared dependency on tiff
DEBUG: Target destroot has no traceable dependency on libsdl-framework
Warning: A creation/deletion/modification was attempted outside sandbox: /.vol/234881026/50782835/6A00D075-FD60-4788-A3A2-1FE5358450D2-2593-000003C1006171CC
Warning: A creation/deletion/modification was attempted outside sandbox: /.vol/234881026/50782835/Framework.dep
Error: Target org.macports.destroot returned: no files matched glob pattern "*"
Warning: the following items did not execute (for libsdl_image-framework): org.macports.destroot
Error: Status 1 encountered during processing.

% sudo port -dt destroot macports-notified
<snip>
** BUILD SUCCEEDED **
DEBUG: Executing proc-post-org.macports.destroot-destroot-0
xinstall: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_sysutils_macports-notifier/work/trunk/build/macports-sync-agent -> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_re
DEBUG: Executing destroot_finish
DEBUG: checking for mtree violations
Warning: A creation/deletion/modification was attempted outside sandbox: /.vol/234881026/50783274/207F8AB3-5337-4D28-A388-81D7D1972178-2876-000003C1EC73DF6B
Warning: A creation/deletion/modification was attempted outside sandbox: /.vol/234881026/50783274/PortsHelper.dep
Warning: A creation/deletion/modification was attempted outside sandbox: /.vol/234881026/50783287/17D8E903-791C-48FB-B16A-300F58C4C7FA-2876-000003C1EC724FF0
Warning: A creation/deletion/modification was attempted outside sandbox: /.vol/234881026/50783287/PortsNotifier.dep

[nox@…]

Some new discussions on macports-dev lead to the conclusion that this bug is related to mtree violations.

[mww@…]

I've just changed the mtree-checker in portdestroot.tcl to also allow files in /Applications and /Library; if we dont manage to get 1.5.1 out quickly, it is possible to set "destroot.violate_mtree yes" [see portfile(7)] to disable the check for a specific port.

[nox@…]

I think that does not explain those weird /.vol mtree violations.

[mww@…]

which weird /.vol mtree violations? The error examples all fail because there are no files in $prefix;

[nox@…]

Why do you talk about $prefix? They are xcode-based framework ports, they go in ${destroot}/Library/Frameworks, and there _are_ files in ${destroot}/Library/Frameworks:

% ls work/destroot/Library/Frameworks/SDL.framework
Headers  Resources  SDL  Versions

An interesting thread about this problem

[nox@…]

Just realised I've misread the thread I've linked, so the thread and you say this error is related to another already-fixed-in-trunk problem.