May 2007 - macports-dev - lists.macosforge.org

Don't print messages inside platform directives
by Ryan Schmidt 25 May '07

25 May '07

A user on macports-users reported this problem, which I can confirm: On May 25, 2007, at 15:03, Valentin Kuznetsov wrote: > When I run portindex I've got 0 errors, but along the output lines > I saw: > Error: ==== ATTENTION!!!! ==== > Error: Sockstat is not working under darwin 8 nor tiger. Please use > Error: lsof -i6/lsof -i4/lsof -U instead. > Error: ==== ATTENTION!!!! ==== I also see the message just by typing "port info sockstat", which is likely due to recent changes to "port info": $ port info sockstat Error: ==== ATTENTION!!!! ==== Error: Sockstat is not working under darwin 8 nor tiger. Please use Error: lsof -i6/lsof -i4/lsof -U instead. Error: ==== ATTENTION!!!! ==== Error: Please sudo port uninstall sockstat sockstat 1.6.2.6, sysutils/sockstat (Variants: universal, darwin_8) http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.bin/sockstat/? hideattic=0&only_with_tag=RELENG_4_9 The sockstat command lists open Internet or UNIX domain sockets. Current version of sockstat from FreeBSD is written in C while this old version is still in Perl. This program is from FreeBSD's source tree. Platforms: darwin Maintainers: mjhsieh(a)yahoo.com sysutils/sockstat does this: platform darwin 8 { ui_error "==== ATTENTION!!!! ====" ui_error "Sockstat is not working under darwin 8 nor tiger. Please use" ui_error "lsof -i6/lsof -i4/lsof -U instead." ui_error "==== ATTENTION!!!! ====" ui_error "Please sudo port uninstall sockstat" } I don't think we should be outputting any messages of any kind in platform variants which MacPorts auto-selects, because they get executed at all sorts of times where outputting messages is not appropriate. Instead, I believe the port should do something like this if it wants to output a message: platform darwin 8 {} pre-fetch { if { [variant_isset darwin_8] } { ui_error "==== ATTENTION!!!! ====" ui_error "Sockstat is not working under darwin 8 nor tiger. Please use" ui_error "lsof -i6/lsof -i4/lsof -U instead." ui_error "==== ATTENTION!!!! ====" ui_error "Please sudo port uninstall sockstat" } } I'm also concerned that the port would output a message saying that the port is not compatible with Tiger, yet not prevent installation on Tiger. It should exit after printing that message. Well, the message should be reworded too, since it's not a forgone conclusion that the user already has sockstat installed at the point that they see the message. The user may be trying to install it for the first time, in which case an uninstall is not necessary or possible. Finally, it's not clear why we are preventing the port from installing on 10.4. Will it work on earlier OS versions like 10.3 or 10.2? I assume yes. What about later OS versions like 10.5? I assume no, but I don't know for sure. The port description, or at least a comment in the portfile, should explain this, and if it's expected that the port won't work on 10.5 either, then darwin 9 should be excluded also.

2 5

Re: [25589] trunk/dports
by Ryan Schmidt 25 May '07

25 May '07

On May 25, 2007, at 13:32, source_changes(a)macosforge.org wrote: > Revision: 25589 > http://trac.macosforge.org/projects/macports/changeset/25589 > Author: nox(a)macports.org > Date: 2007-05-25 11:32:15 -0700 (Fri, 25 May 2007) > > Log Message: > ----------- > Changed maintainer mail address (use new obfuscation policy). > > Modified Paths: > -------------- > trunk/dports/devel/icu/Portfile > trunk/dports/devel/poco/Portfile > trunk/dports/shells/zsh-devel/Portfile > > Modified: trunk/dports/devel/icu/Portfile > =================================================================== > --- trunk/dports/devel/icu/Portfile 2007-05-25 14:01:44 UTC (rev > 25588) > +++ trunk/dports/devel/icu/Portfile 2007-05-25 18:32:15 UTC (rev > 25589) > @@ -7,7 +7,7 @@ > revision 1 > categories devel > platforms darwin > -maintainers n.oxyde(a)gmail.com > +maintainers nox > description International Components for Unicode [snip] Is that the new policy now? I know we talked about it on the list, but I didn't realize it had been finally decided. And if it has, then surely it should be changed in all portfiles at once, and not left to each port author to do.

1 0

NEW: math/qhull port
by Mark Moll 25 May '07

25 May '07

Can somebody commit this: http://trac.macports.org/projects/macports/ticket/11990 NEW: qhull 2003.1 New port for the qhull package. Qhull computes the convex hull, Delaunay triangulation, Voronoi diagram, halfspace intersection about a point, furthest-site Delaunay triangulation, and furthest-site Voronoi diagram. The software runs in 2-d, 3-d, 4-d, and higher dimensions. Qhull implements the Quickhull algorithm for computing the convex hull. It handles roundoff errors from floating point arithmetic. Qhull also computes volumes, surface areas, and approximations to the convex hull. -- Mark

2 1

Re: [25475] trunk/dports/lang/itcl/Portfile
by Ryan Schmidt 25 May '07

25 May '07

On May 22, 2007, at 11:10, source_changes(a)macosforge.org wrote: > Get tcl headers by downloading the full tcl from sourceforge > instead of a custom tarball on the defunct opendarwin site. Since your port depends on port:tcl, wouldn't it be better to use the tcl tarball already downloaded by the tcl port, rather than download it again? I believe someone recently posted instructions on how to do that.

2 2

Strange error
by Randall Wood 23 May '07

23 May '07

When running port from within the Apple Security Frameworks, I get this error: couldn't find HOME environment variable to expand path while executing "file mkdir $macports_user_dir" (procedure "dportinit" line 45) invoked from within "dportinit ui_options global_options global_variations" Error: /opt/local/bin/port: Failed to initialize ports system, couldn't find HOME environment variable to expand path How should I mark this when I report it as an error in trac to ensure proper action? Randall Wood rhwood(a)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."

3 8

Re: [25482] trunk/dports/x11/iwidgets/Portfile
by Juan Manuel Palacios 23 May '07

23 May '07

Hi Mark! On May 22, 2007, at 3:37 PM, source_changes(a)macosforge.org wrote: >> -set tclconfig ${prefix}/lib > > +configure.env TCLROOT=${prefix} \ > + LDFLAGS="-L${prefix}/lib -ltcl -L/usr/X11R6/lib -lX11" > + Shouldn't you remove that first LDFLAG? MacPorts now provides a default -L${prefix}/lib value for LDFLAGS, so there might be no need to provide it here. Regards,... -jmpp

1 0

Re: [25441] trunk/dports/print/ghostscript/Portfile
by Ryan Schmidt 22 May '07

22 May '07

On May 22, 2007, at 00:39, source_changes(a)macosforge.org wrote: > +# MacPorts 1.4.1 or higher adds -I${prefix}/include and -L$ > {prefix}/lib flags to the configure by default. > +# This change may break building ghostscript. Here is a workaround > to avoid this issue. > +configure.cppflags {} > +configure.ldflags {} That seems to work... That is, +universal seems to build a universal binary: $ file /opt/local/bin/gs /opt/local/bin/gs: Mach-O universal binary with 2 architectures /opt/local/bin/gs (for architecture i386): Mach-O executable i386 /opt/local/bin/gs (for architecture ppc): Mach-O executable ppc It looks like ghostscript makes use of installed X libraries: $ otool -L /opt/local/bin/gs /opt/local/bin/gs: /usr/X11R6/lib/libXt.6.dylib (compatibility version 6.0.0, current version 6.0.0) /usr/X11R6/lib/libSM.6.dylib (compatibility version 6.0.0, current version 6.0.0) /usr/X11R6/lib/libICE.6.dylib (compatibility version 6.3.0, current version 6.3.0) /usr/X11R6/lib/libXext.6.dylib (compatibility version 6.4.0, current version 6.4.0) /usr/X11R6/lib/libX11.6.dylib (compatibility version 6.2.0, current version 6.2.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.3.7) So you should probably add depends_lib lib:libX11.6:XFree86 to the portfile.

1 0

Can't upgrade python24
by Vincent Lefevre 22 May '07

22 May '07

I want to upgrade to python24 @2.4.4_1, but I get the following error: prunille:~> sudo port -v -d upgrade python24 DEBUG: Found port in file:///Users/vinc17/software/dports/lang/python24 DEBUG: Found port in file:///opt/local/var/db/dports/sources/rsync.rsync.macports.org_dpupdate_dports/lang/python24 ---> Activating python24 2.4.4_0+darwin_8 DEBUG: Image error: Another version of this port (python24 @2.4.3_1+darwin_8) is already active. while executing "portimage::activate $portname $version_installed$variant $optionslist" Error: Activating python24 2.4.4_0 failed: Image error: Another version of this port (python24 @2.4.3_1+darwin_8) is already active. Adding @2.4.4_1 doesn't change anything. Anyone knows what's wrong? A bug in "port upgrade"? FYI: prunille:~> port installed python24 The following ports are currently installed: python24 @2.4.3_1+darwin_8 (active) python24 @2.4.4_0+darwin_8 prunille:~> port info python24 Warning: Found 2 port python24 definitions, displaying first one. python24 2.4.4, Revision 1, lang/python24 (Variants: universal, puredarwin, darwin_8) http://www.python.org/ Python is an interpreted, interactive, object-oriented programming language. Library Dependencies: gettext Platforms: darwin Maintainers: mww(a)macports.org prunille:~> port version Version: 1.442 The PortIndex file is up-to-date. -- Vincent Lefèvre <vincent(a)vinc17.org> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

3 4

DarwinPortStartup
by James Cox 22 May '07

22 May '07

All, we've still got a few ports relying on this port, however opendarwin.org is now off the air, where the binaries are located. so we either (re)host these binaries elsewhere, or fix the remaining handful of ports still requiring them... mysql being a predominate example. Best... james -- James Cox, Internet Consultant e: james(a)imaj.es w: http://imaj.es/ -- James Cox, Internet Consultant t: 07968 349990 e: james(a)imaj.es w: http://imaj.es/

3 3

Re: [25413] trunk/dports/print/ghostscript/Portfile
by Ryan Schmidt 22 May '07

22 May '07

On May 21, 2007, at 11:36, source_changes(a)macosforge.org wrote: > Revision: 25413 > http://trac.macosforge.org/projects/macports/changeset/25413 > Author: digdog(a)macports.org > Date: 2007-05-21 09:36:54 -0700 (Mon, 21 May 2007) > > Log Message: > ----------- > patch for #11901 > > Modified Paths: > -------------- > trunk/dports/print/ghostscript/Portfile > > Modified: trunk/dports/print/ghostscript/Portfile > =================================================================== > --- trunk/dports/print/ghostscript/Portfile 2007-05-21 16:28:48 UTC > (rev 25412) > +++ trunk/dports/print/ghostscript/Portfile 2007-05-21 16:36:54 UTC > (rev 25413) > @@ -26,6 +26,12 @@ > ghostscript-fonts-std-8.11.tar.gz md5 > 6865682b095f8c4500c54b285ff05ef6 \ > ghostscript-fonts-other-6.0.tar.gz md5 > 1a643ae62ef166562e4d422b1a601272 > > +configure { > + # MacPorts 1.4.1 or higher adds -I${prefix}/include and -L$ > {prefix}/lib flags to the configure by default. > + # This change may break building ghostscript. Here is a > workaround to avoid this issue. > + system "cd $worksrcpath && ./configure --prefix=${prefix}" > +} > + > build.target > > destroot.destdir prefix=${destroot}/${prefix} How does the MacPorts change break ghostscript? And are you sure this is the best solution? Wouldn't it be better to just remove the -I$ {prefix}/include and -L${prefix}/lib flags from their respective variables? I think doing it the way you're doing it may break other things, since now you're not having any of the env variables that MacPorts uses. I'm guessing this would also break the +universal variant (if in fact it ever worked with ghostscript).

3 2