On 2007-08-15 01:29:09 -0400, Ryan Schmidt <[EMAIL PROTECTED]> said:


On Aug 14, 2007, at 22:23, Sean Fulton wrote:

On 2007-08-13 02:40:21 -0400, Anders F Björklund said:

mpu78 wrote:

I'm a Unix user who is new to Mac and MacPorts. I've just started

installing
things using `port' today, i.e. after the release of MacPorts  1.5.1, which I
understand does these `mtree' checks.
I'm not able to install much without getting the "mtree  violation" error. It
fails to install `Xemacs' with:
Error: violation by /opt/local/man
Error: Target org.macports.destroot returned: mtree violation!
and `gnome-doc-utils' with the same error on the way to  installing other
things.
What should I do?

Downgrade to MacPorts-1.5.0, upgrade to SVN trunk, or wait until next release...
--anders

Are maintainers supposed to be fixing these errors somehow? I maintain a port that has this error and I don't know if I'm supposed to add
        destroot.violate_mtree yes
or let it go until the next release.

Yes, you are supposed to be fixing this. You are not supposed to be violating the mtree. The next release of MacPorts will downgrade these from fatal errors to warnings, but that's only temporary, until
people fix the ports. For example, if you are installing things into /
opt/local/man, you should change your port to install those things into /opt/local/share/man. If you are installing things into other nonstandard places, you should evaluate whether those were intentional or not. If intentional, then you can add "destroot.violate_mtree yes" to the portfile to indicate this intent. If you are installing things in places that are being reported as an mtree violation, but you do not believe it is, then you should report
that to the -dev list where it can be decided whether or not to amend
the mtree checker.

OK, thanks. Is there documentation for the mtree standards?

        Sean


_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-users

Reply via email to