October 2010 - macports-changes - lists.macosforge.org

[72784] trunk/base/src/pextlib1.0/system.c
by jmr＠macports.org 26 Oct '10

26 Oct '10

Revision: 72784 http://trac.macports.org/changeset/72784 Author: jmr(a)macports.org Date: 2010-10-26 13:14:35 -0700 (Tue, 26 Oct 2010) Log Message: ----------- explicitly point to the log file when the system command fails Modified Paths: -------------- trunk/base/src/pextlib1.0/system.c Modified: trunk/base/src/pextlib1.0/system.c =================================================================== --- trunk/base/src/pextlib1.0/system.c 2010-10-26 19:34:37 UTC (rev 72783) +++ trunk/base/src/pextlib1.0/system.c 2010-10-26 20:14:35 UTC (rev 72784) @@ -256,7 +256,7 @@ ui_info(interp, errorstr); free(errorstr); } - Tcl_SetObjResult(interp, Tcl_NewStringObj("shell command failed", -1)); + Tcl_SetObjResult(interp, Tcl_NewStringObj("shell command failed (see log for details)", -1)); } }

1 0

[72783] trunk/base/src/package1.0
by jmr＠macports.org 26 Oct '10

26 Oct '10

Revision: 72783 http://trac.macports.org/changeset/72783 Author: jmr(a)macports.org Date: 2010-10-26 12:34:37 -0700 (Tue, 26 Oct 2010) Log Message: ----------- reacquire root privileges for dmg/mdmg (doesn't seem like this should be necessary, but hdiutil claims "permission denied" otherwise...) Modified Paths: -------------- trunk/base/src/package1.0/portdmg.tcl trunk/base/src/package1.0/portmdmg.tcl Modified: trunk/base/src/package1.0/portdmg.tcl =================================================================== --- trunk/base/src/package1.0/portdmg.tcl 2010-10-26 19:34:05 UTC (rev 72782) +++ trunk/base/src/package1.0/portdmg.tcl 2010-10-26 19:34:37 UTC (rev 72783) @@ -45,9 +45,13 @@ proc portdmg::dmg_main {args} { global name version revision package.destpath UI_PREFIX - + ui_msg "$UI_PREFIX [format [msgcat::mc "Creating disk image for %s-%s"] ${name} ${version}]" - + + if {[getuid] == 0 && [geteuid] != 0} { + setegid 0; seteuid 0 + } + return [package_dmg $name $version $revision] } Modified: trunk/base/src/package1.0/portmdmg.tcl =================================================================== --- trunk/base/src/package1.0/portmdmg.tcl 2010-10-26 19:34:05 UTC (rev 72782) +++ trunk/base/src/package1.0/portmdmg.tcl 2010-10-26 19:34:37 UTC (rev 72783) @@ -45,9 +45,13 @@ proc portmdmg::mdmg_main {args} { global name version revision package.destpath UI_PREFIX - + ui_msg "$UI_PREFIX [format [msgcat::mc "Creating disk image for %s-%s"] ${name} ${version}]" - + + if {[getuid] == 0 && [geteuid] != 0} { + setegid 0; seteuid 0 + } + return [package_mdmg $name $version $revision] }

1 0

[72782] trunk/dports/science/root/Portfile
by michaelld＠macports.org 26 Oct '10

26 Oct '10

Revision: 72782 http://trac.macports.org/changeset/72782 Author: michaelld(a)macports.org Date: 2010-10-26 12:34:05 -0700 (Tue, 26 Oct 2010) Log Message: ----------- root: addresses ticket #26984. Move qt4 portgroup inclusion to the main level from inside variant. Modified Paths: -------------- trunk/dports/science/root/Portfile Modified: trunk/dports/science/root/Portfile =================================================================== --- trunk/dports/science/root/Portfile 2010-10-26 18:26:52 UTC (rev 72781) +++ trunk/dports/science/root/Portfile 2010-10-26 19:34:05 UTC (rev 72782) @@ -178,8 +178,11 @@ depends_lib-append port:qt4-x11 } +if {[variant_isset qt_mac]} { + PortGroup qt4 1.0 +} + variant qt_mac conflicts qt_x11 description {Builds port with Qt support via Mac UI} { - PortGroup qt4 1.0 post-patch { # fix where "qglobal.h" is found in all files that use or reference it foreach tpf { configure graf2d/qt/src/TGQt.cxx } {

1 0

[72781] trunk/dports/games/wop/
by jmr＠macports.org 26 Oct '10

26 Oct '10

Revision: 72781 http://trac.macports.org/changeset/72781 Author: jmr(a)macports.org Date: 2010-10-26 11:26:52 -0700 (Tue, 26 Oct 2010) Log Message: ----------- wop: delete broken port, closes #18768 Removed Paths: ------------- trunk/dports/games/wop/

1 0

[MacPorts] FAQ modified
by MacPorts 26 Oct '10

26 Oct '10

Changed page "FAQ" by devans(a)macports.org from 76.102.85.150* Page URL: <https://trac.macports.org/wiki/FAQ> Diff URL: <https://trac.macports.org/wiki/FAQ?action=diff&version=106> Revision 106 -------8<------8<------8<------8<------8<------8<------8<------8<-------- Index: FAQ ========================================================================= --- FAQ (version: 105) +++ FAQ (version: 106) @@ -38,7 +38,7 @@ === Is MacPorts Universal? === #universal -MacPorts works on both Intel- and PowerPC-based Macs, but the ports you install will be compiled only for the architecture you're currently running on. This means that if you migrate from, say, a PowerPC Mac to an Intel one and use Migration Assistant to copy your data to the new machine, you should reinstall all your ports on the new machine to rebuild them for Intel. See the Migration link in the previous question. +MacPorts works on both Intel- and PowerPC-based Macs, but, by default, the ports you install will be compiled only for the architecture you're currently running on. This means that if you migrate from, say, a PowerPC Mac to an Intel one and use Migration Assistant to copy your data to the new machine, you should reinstall all your ports on the new machine to rebuild them for Intel. See the Migration link in the previous question. For many ports, there's now an alternative: select the +universal variant when you build each port, and MacPorts will create universal binaries that work on multiple processor architectures. The set of architectures is controlled by the `universal_archs` setting in [http://guide.macports.org/chunked/internals.configuration-files.html#intern… macports.conf]. -------8<------8<------8<------8<------8<------8<------8<------8<-------- * The IP shown here might not mean anything if the user or the server is behind a proxy. -- MacPorts <http://www.macports.org/> Ports system for Mac OS This is an automated message. Someone at http://www.macports.org/ added your email address to be notified of changes on FAQ. If it was not you, please report to .

1 0

[MacPorts] FAQ modified
by MacPorts 26 Oct '10

26 Oct '10

Changed page "FAQ" by jmr(a)macports.org from 210.215.87.80* Page URL: <https://trac.macports.org/wiki/FAQ> Diff URL: <https://trac.macports.org/wiki/FAQ?action=diff&version=105> Revision 105 Comment: update universal section -------8<------8<------8<------8<------8<------8<------8<------8<-------- Index: FAQ ========================================================================= --- FAQ (version: 104) +++ FAQ (version: 105) @@ -38,13 +38,17 @@ === Is MacPorts Universal? === #universal -MacPorts works on both Intel- and PowerPC-based Macs, but the ports you install will be compiled only for the architecture you're currently running on. This means that if you migrate from, say, a PowerPC Mac to an Intel one and use Migration Assistant to copy your data to the new machine, you should reinstall all your ports on the new machine to rebuild them for Intel. It may be simpler to completely remove all of MacPorts and start fresh. See below for uninstallation instructions, but be sure to keep any configuration files you need. - -For many ports, there's now an alternative: select the +universal variant when you build each port, and MacPorts will create universal binaries that work on both Intel and PowerPC. This can be useful if you anticipate migrating to a different Mac soon, or if you want to install MacPorts on an external hard drive that's used by both Intel- and PowerPC-based Macs. But note that because +universal is new, it may not work correctly for all ports, even if no error message is shown during installation. If you find a port that will not build with +universal, or if it builds but then does not work correctly, please file a bug report. If you can provide a patch to fix the problem, that's even better. - -Some ports may only work on PowerPC Macs or only on Intel Macs. In some cases, these are bugs that need to be fixed. If there is a newer version of the software available, you should report this to the port maintainer. Maybe the new version works correctly on both architectures. If the port is already using the latest version, report the problem to the upstream authors of the software; the software may need to be updated. In other cases, the software may be specifically written for one processor architecture such that it will not be possible to make it available to the other. - -See also [wiki:Universal] for a list of ports that were tested for +universal support and the results. +MacPorts works on both Intel- and PowerPC-based Macs, but the ports you install will be compiled only for the architecture you're currently running on. This means that if you migrate from, say, a PowerPC Mac to an Intel one and use Migration Assistant to copy your data to the new machine, you should reinstall all your ports on the new machine to rebuild them for Intel. See the Migration link in the previous question. + +For many ports, there's now an alternative: select the +universal variant when you build each port, and MacPorts will create universal binaries that work on multiple processor architectures. The set of architectures is controlled by the `universal_archs` setting in [http://guide.macports.org/chunked/internals.configuration-files.html#intern… macports.conf]. + +Using +universal can allow you to run ports which do not build for your preferred architecture alongside those that do. For example, the wine port only builds for i386, but shares many dependencies with ports that can build for x86_64. On x86_64 hardware, the dependencies can be built with +universal so they support both i386 and x86_64 dependents. + +Historically, +universal could also be useful if you anticipated migrating to a different Mac soon, or if you wanted to install MacPorts on an external hard drive used by both Intel- and PowerPC-based Macs. But note that because +universal is not necessarily tested by port maintainers, it may not work correctly for all ports, even if no error message is shown during installation. If you find a port that will not build with +universal, or if it builds but then does not work correctly, please file a bug report. If you can provide a patch to fix the problem, that's even better. + +Some ports may only work on PowerPC Macs or only on Intel Macs. Others may work on 32-bit archs but not 64-bit. In some cases, these are bugs that need to be fixed. If there is a newer version of the software available, you should report this to the port maintainer. Maybe the new version works correctly on both architectures. If the port is already using the latest version, report the problem to the upstream authors of the software; the software may need to be updated. In other cases, the software may be specifically written for one processor architecture such that it will not be possible to make it available to the other. + +See also [wiki:Universal] for a (highly outdated at this point) list of ports that were tested for +universal support and the results. === Why is /opt/local the default install location for MacPorts? === #defaultprefix -------8<------8<------8<------8<------8<------8<------8<------8<-------- * The IP shown here might not mean anything if the user or the server is behind a proxy. -- MacPorts <http://www.macports.org/> Ports system for Mac OS This is an automated message. Someone at http://www.macports.org/ added your email address to be notified of changes on FAQ. If it was not you, please report to .

1 0

[72780] trunk/dports/devel/qjson/Portfile
by snc＠macports.org 26 Oct '10

26 Oct '10

Revision: 72780 http://trac.macports.org/changeset/72780 Author: snc(a)macports.org Date: 2010-10-26 10:37:28 -0700 (Tue, 26 Oct 2010) Log Message: ----------- qjson: use KDE4-1.1 PortGroup Modified Paths: -------------- trunk/dports/devel/qjson/Portfile Modified: trunk/dports/devel/qjson/Portfile =================================================================== --- trunk/dports/devel/qjson/Portfile 2010-10-26 17:22:24 UTC (rev 72779) +++ trunk/dports/devel/qjson/Portfile 2010-10-26 17:37:28 UTC (rev 72780) @@ -2,10 +2,11 @@ # $Id$ PortSystem 1.0 -PortGroup kde4 1.0 +PortGroup kde4 1.1 name qjson version 0.7.1 +revision 1 categories devel kde4 kde maintainers snc openmaintainer description map JSON data to QVariant objects

1 0

[MacPorts] FAQ modified
by MacPorts 26 Oct '10

26 Oct '10

Changed page "FAQ" by jmr(a)macports.org from 210.215.87.80* Page URL: <https://trac.macports.org/wiki/FAQ> Diff URL: <https://trac.macports.org/wiki/FAQ?action=diff&version=104> Revision 104 Comment: update Xcode upgrading info -------8<------8<------8<------8<------8<------8<------8<------8<-------- Index: FAQ ========================================================================= --- FAQ (version: 103) +++ FAQ (version: 104) @@ -31,7 +31,7 @@ === How do I upgrade my Xcode install? === #upgradexcode -Some ports need newer versions of Xcode than that which ships with the OS, and will fail to install due to that requirement. Xcode is not updated via Software Update, you have to download it manually. To do so, go to http://connect.apple.com/ and log in with your ADC information (the free online account is enough to get access to Xcode). Once you log in, go to ''Downloads'', then select ''Developer Tools'' on the right section under ''Downloads''. You can then search for Xcode (there are quite a few versions available, make sure to get the latest for your OS version) using your browser, via Cmd-F. +Some ports need newer versions of Xcode than that which ships with the OS, and will fail to install with older versions due to that requirement. Apple has begun updating Xcode via Software Update on Mac OS X 10.6, but on older OS releases you have to download new Xcode versions manually. To do so, go to http://connect.apple.com/ and log in with your Apple ID (the free online developer account is enough to get access to Xcode). Once you log in, go to ''Downloads'', then select ''Developer Tools'' on the right section under ''Downloads''. You can then search for Xcode (there are quite a few versions available, make sure to get the latest for your OS version) using your browser, via Cmd-F. === Will my MacPorts install continue to work after installing a new major OS release or migrating to a new machine with a different CPU architecture? === #migration In general the answer is no. See [wiki:Migration] for how to get things working again. -------8<------8<------8<------8<------8<------8<------8<------8<-------- * The IP shown here might not mean anything if the user or the server is behind a proxy. -- MacPorts <http://www.macports.org/> Ports system for Mac OS This is an automated message. Someone at http://www.macports.org/ added your email address to be notified of changes on FAQ. If it was not you, please report to .

1 0

[MacPorts] FAQ modified
by MacPorts 26 Oct '10

26 Oct '10

Changed page "FAQ" by jmr(a)macports.org from 210.215.87.80* Page URL: <https://trac.macports.org/wiki/FAQ> Diff URL: <https://trac.macports.org/wiki/FAQ?action=diff&version=103> Revision 103 Comment: fix sentence about HOWTOs to make sense -------8<------8<------8<------8<------8<------8<------8<------8<-------- Index: FAQ ========================================================================= --- FAQ (version: 102) +++ FAQ (version: 103) @@ -1,4 +1,4 @@ -There is also a [wiki:howto HOWTO section], which may answer your questions not listed here and provides useful tutorials for all sorts of using MacPorts. +There is also a [wiki:howto HOWTO section], which may answer some questions not listed here and provides useful tutorials for performing a number of different tasks using MacPorts. [[PageOutline(2-3,Table of Contents,inline)]] -------8<------8<------8<------8<------8<------8<------8<------8<-------- * The IP shown here might not mean anything if the user or the server is behind a proxy. -- MacPorts <http://www.macports.org/> Ports system for Mac OS This is an automated message. Someone at http://www.macports.org/ added your email address to be notified of changes on FAQ. If it was not you, please report to .

1 0

[72779] trunk/dports/graphics/librsvg/Portfile
by elelay＠macports.org 26 Oct '10

26 Oct '10

Revision: 72779 http://trac.macports.org/changeset/72779 Author: elelay(a)macports.org Date: 2010-10-26 10:22:24 -0700 (Tue, 26 Oct 2010) Log Message: ----------- update librsvg to 2.32.0 the older version was incompatible with gdk-pixbuf > 2.21.3 because it installed some of its libraries in lib/gtk-2.0/2.10.0/loaders instead of lib/gdk-pixbuf-2.0/2.10.0/loaders hence was not found by gdk-pixbuf. a simple test with py26-gtk installed is python -c "import gtk;print gtk.gdk.pixbuf_get_formats()" | grep svg which should output a line Modified Paths: -------------- trunk/dports/graphics/librsvg/Portfile Modified: trunk/dports/graphics/librsvg/Portfile =================================================================== --- trunk/dports/graphics/librsvg/Portfile 2010-10-26 17:05:37 UTC (rev 72778) +++ trunk/dports/graphics/librsvg/Portfile 2010-10-26 17:22:24 UTC (rev 72779) @@ -5,7 +5,7 @@ PortGroup archcheck 1.0 name librsvg -version 2.26.3 +version 2.32.0 license GPL-2 LGPL-2 set branch [join [lrange [split ${version} .] 0 1] .] categories graphics gnome @@ -20,9 +20,9 @@ master_sites gnome:sources/${name}/${branch}/ use_bzip2 yes -checksums md5 8df68c2c02cdf2a96a92b43bf737bf9c \ - sha1 ef0063eaa9e638364cc8ff142aadef8a267b7af5 \ - rmd160 14f51ae7997d8137e618ee117ef7980fc0ffe52c +checksums md5 b015a9bd80143ec876af489d882dc28b \ + sha1 252727b948a29b36dae0022e0c620538bcb158f8 \ + rmd160 9d89f333544d8eb66698c94602ea93ac3ba01157 depends_build port:pkgconfig @@ -51,8 +51,6 @@ lib/libpango-1.0.dylib \ lib/libxml2.dylib -configure.args --disable-mozilla-plugin - post-destroot { set python.branch 2.6 set python.bin ${frameworks_dir}/Python.framework/Versions/${python.branch}/bin/python${python.branch} @@ -67,7 +65,7 @@ post-activate { ui_debug "Updating gdk-pixbuf.loaders..." - system "gdk-pixbuf-query-loaders >${prefix}/etc/gtk-2.0/gdk-pixbuf.loaders" + system "gdk-pixbuf-query-loaders --update-cache" } livecheck.type regex

1 0