I have noticed that almost 1840 ports have configure.args set to install man pages in ${prefix}/share/man instead of the default location ${prefix}/man and that the mtree-violation code does not like ${prefix}/man. Can we allow ${prefix}/man to be used and perhaps even set it to be the preferred location for man pages since it seems to fit more with the UNIX default location? On 13 Aug 2007, at 19:23, susanmackay@optusnet.com.au wrote:
I'm trying to install gnome-doc-utils and I get the following (just the last output lines - all lines above appeared to be 'normal' operation):
/usr/bin/install -c -m 644 gnome-doc-xslt-C.omf /opt/local/var/ macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_ports_gnome_gnome-doc-utils/work/destroot/opt/local/ share/omf/g nome-doc-xslt/gnome-doc-xslt-C.omf make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[2]: Nothing to be done for `install-exec-am'. test -z "/opt/local/share/gnome-doc-utils" || /bin/sh ./ mkinstalldirs "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macport s.org_release_ports_gnome_gnome-doc-utils/work/destroot/opt/local/ share/gnom e-doc-utils" /usr/bin/install -c -m 644 'template.omf.in' '/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macport s.org_release_ports_gnome_gnome-doc-utils/work/destroot/opt/local/ share/gnom e-doc-utils/template.omf.in' /usr/bin/install -c -m 644 'template.make' '/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macport s.org_release_ports_gnome_gnome-doc-utils/work/destroot/opt/local/ share/gnom e-doc-utils/template.make' /usr/bin/install -c -m 644 'template-document.xml' '/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macport s.org_release_ports_gnome_gnome-doc-utils/work/destroot/opt/local/ share/gnom e-doc-utils/template-document.xml' DEBUG: Executing destroot_finish DEBUG: checking for mtree violations Error: violation by /opt/local/man Error: Target org.macports.destroot returned: mtree violation! Warning: the following items did not execute (for gnome-doc-utils): org.macports.activate org.macports.destroot org.macports.install Error: Status 1 encountered during processing. Titania:~ susan$ sudo port -dv install gnome-doc-utils
(The last line is there to show the command I used).
I had recently ( as in about 1200UTC 13/8/2007) done a selfupdate and a sync which included several new versions of some packages. These were 'upgraded' beforehand.
Is there something I have to do to get this to work?
Thanks
Susan _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Randall Wood rhwood@mac.com http://shyramblings.blogspot.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy."
Le 14 août 07 à 03:17, Randall Wood a écrit :
I have noticed that almost 1840 ports have configure.args set to install man pages in ${prefix}/share/man instead of the default location ${prefix}/man and that the mtree-violation code does not like ${prefix}/man.
Can we allow ${prefix}/man to be used and perhaps even set it to be the preferred location for man pages since it seems to fit more with the UNIX default location?
See hier(7), share/man _is_ the preferred location for manpages. -- Anthony Ramine, the infamous MacPorts Trac slave. nox@macports.org
On 14/08/2007, at 11:17, Randall Wood wrote:
Can we allow ${prefix}/man to be used and perhaps even set it to be the preferred location for man pages since it seems to fit more with the UNIX default location?
From what I can tell, all major Linux distributions have moved to placing man pages into ${prefix}/share/man (either with prefix = /usr or /usr/local), in line with the File Hierarchy Standard [1], and FreeBSD [2], OpenBSD [3] and NetBSD [4] all do the same, with the point being to isolate all read-only architecture independent data into ${prefix}/share. Indeed, Mac OS X's own hier(7) man page recommends the same thing. In addition, it's not much trouble at all to make a port install man pages into ${prefix}/share/man; in most cases, we either pass -- mandir=${prefix}/share/man to configure or copy it ourselves. (I suspect that most of the ports that install man pages into ${prefix}/ man are using configure script generated by autoconf < 2.59c, as it was only at that revision that it changed its default mandir to $ {prefix}/share/man.) Consequently, I think we should stick with installing man pages into ${prefix}/share/man. As for how to deal with the breaking of builds, however, it seems to me that we should either push out a revision incorporating mtree violation as a warning rather than an error (rescinding that when we've fixed the ports currently in the tree), or temporarily allow non-maintainers to commit patches that only change the man page installation location. Hopefully one of these paths would be fairly convenient to implement. KInd regards, Maun Suang [1] http://www.pathname.com/fhs/pub/ fhs-2.3.html#USRSHAREARCHITECTUREINDEPENDENTDATA [2] http://www.freebsd.org/cgi/man.cgi?query=hier [3] http://www.openbsd.org/cgi-bin/man.cgi?query=hier&sektion=7 [4] http://netbsd.gw.com/cgi-bin/man-cgi?hier+7+NetBSD-current -- Boey Maun Suang (Boey is my surname) Email: boeyms at macports dot org
participants (3)
-
Boey Maun Suang
-
N_Ox
-
Randall Wood