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

New website! ... not yet, really (Fwd: [28303] trunk/www)
by Juan Manuel Palacios 05 Sep '07

05 Sep '07

Good evening everyone! I am most glad to announce that thanks to the work I've been putting into the PortIndex2MySQL.tcl script lately, I was able to recover our old web site back from the dead as a natural progression to the former, as you may have seen from my recent commit r28303. The result is posted at my web server, http://apollo.homeunix.net/macports, reflecting the state of the current trunk/www dir in svn at any moment. Nevertheless, what you'll see there is no more than the bringing up to speed of the old content with current information, but it is otherwise the same site we used to have back in OpenDarwin days (the "not yet" part of this message's title, unfortunately). While at it I also restructured the sources a bit, moving files here and there to have a cleaner layout, only editing the English pages and moving all other languages into a 'localized' dir, though. The really important part, however, is the revival of the ports.php page, which many users have been craving for ever since we moved to Mac OS Forge. I'm feeding this page with live information off our ports tree by running the PortIndex2MySQL.tcl script locally, though not automated yet (so lag is to be expected). Surely many things will seem broken (links maybe --surely for any language other than English--) and/or outdated, certainly including the now aging visual & structural design. Kevin Van Vechten assured me we could host the ports.php page and new guide on Mac OS Forge servers, but I'm more than sure that only from looking at the site it'll be quite obvious that we need a new and revamped design, short of a complete overhaul. In a nutshell, the purpose of this message is to call for a discussion on what we should do with our web site, which is in desperate need of some love, blood and new air. I'm even thinking about calling for an open contest so that anyone can submit new designs and logos for the project to adapt, extending the invitation to our entire user base: users mailing list, irc channel, wordpress post, wiki page, maybe even inviting WebKit people --who naturally have a thing for designing beautiful websites-- and who knows what else... something akin to NetBSD's logo redesign contest some years ago. Even though the rules for such contest would have to be very clearly defined and the entire process might be somewhat involved, I have to admit I'm developing quite a strong inclination for this approach; if anything, it'll surely help spice up interest and involvement with the project from our user base. So to sum up, it would be great to define a roadmap for a revamped web presence before devoting any more energy to what we currently have. Please don't be shy to post your opinions so that we can all start working toward finding the resources we need to make this happen. I am more than happy to lead this effort both in planning and coordination, but one mandatory requirement before moving forward is knowing if I'll have anything to lead ;-) Regards,... -jmpp

8 17

Infrastructure requests
by Juan Manuel Palacios 05 Sep '07

05 Sep '07

Hello all! I recently created a page listing what I believe are the top priority infrastructure requests we have for our Mac OS Forge host, http://trac.macports.org/projects/macports/wiki/InfrastructureRequests Per the introductory text in there: "When thinking about a functionality you may desire at the server level, keep in mind that Mac OS Forge is not only shared with other projects but also that it does not have a staff of dedicated system administrators to cater to every single request. Therefore please refrain from submitting any infrastructure related ticket before presenting a valid case for it on the MacPorts development list and gathering at least some consensus over your proposal. Generally speaking, it's best to channel such requests through the MacPorts management team (jberry, jmpp & mww), since they are the ones in most frequent communication with Mac OS Forge admin personnel and as a result have a better feel for the state of current infrastructure and/ or pending requests." So please do feel free to brainstorm over what I listed on that page and the tickets I linked, but also please do discuss here any modifications you might want to make to it or new request tickets you might want to submit. Thanks for your help in streamlining our feedback channels with our very kind host ;-) Regards,... -jmpp

3 4

Re: [28607] trunk/dports/science/nco/Portfile
by Ryan Schmidt 05 Sep '07

05 Sep '07

On Sep 4, 2007, at 13:14, source_changes(a)macosforge.org wrote: > Revision: 28607 > http://trac.macosforge.org/projects/macports/changeset/28607 > Author: simon(a)macports.org > Date: 2007-09-04 11:14:13 -0700 (Tue, 04 Sep 2007) > > Log Message: > ----------- > science/nco: Updated to version 3.9.1, closes #12274. Maintainer > update, thanks to takeshi(a)mac.com. But you also undid r28515 in the process. Please, put it back. > Modified Paths: > -------------- > trunk/dports/science/nco/Portfile > > Modified: trunk/dports/science/nco/Portfile > =================================================================== > --- trunk/dports/science/nco/Portfile 2007-09-04 16:32:25 UTC (rev > 28606) > +++ trunk/dports/science/nco/Portfile 2007-09-04 18:14:13 UTC (rev > 28607) > @@ -1,14 +1,14 @@ > # $Id$ > PortSystem 1.0 > + > name nco > -version 3.1.9 > -revision 1 > +version 3.9.1 > platforms darwin > maintainers takeshi(a)mac.com > categories science > description The netCDF Operators > master_sites http://${name}.sourceforge.net/src/ > -checksums sha1 b669e64d4eecadc6b4d96ca3c7482a3894fa8ba2 > +checksums sha1 3da4747545c05e34a88c3f2bba4e7f7b7eca1774 > homepage http://nco.sourceforge.net/ > long_description \ > Each NCO operator (e.g., ncks) takes netCDF or HDF > input file(s), \ > @@ -29,17 +29,29 @@ > port:netcdf \ > port:openssl \ > port:udunits \ > - port:zlib > + port:zlib \ > + port:antlr > depends_build port:bison \ > port:m4 > > -patchfiles patch-configure > - > -configure.env MACOSX_DEPLOYMENT_TARGET=10.4 > -configure.cppflags -I/usr/include/malloc > -configure.args --disable-ncoxx --disable-dependency-tracking \ > +configure.env MACOSX_DEPLOYMENT_TARGET=10.4 \ > + CPPFLAGS=-I/usr/include/malloc \ > + HAVE_ANTLR=yes ANTLR_ROOT=${prefix} > +configure.args --disable-dependency-tracking \ > --mandir=${prefix}/share/man [snip]

2 1

Re: [28597] trunk/dports/net
by Ryan Schmidt 05 Sep '07

05 Sep '07

On Sep 4, 2007, at 04:32, source_changes(a)macosforge.org wrote: > Revision: 28597 > http://trac.macosforge.org/projects/macports/changeset/28597 > Author: rhwood(a)macports.org > Date: 2007-09-04 02:32:58 -0700 (Tue, 04 Sep 2007) > > Log Message: > ----------- > Adium is a chat client for OS X. [snip] Why a portfile for Adium? It's easily downloadable as a disk image from the project's web site and already includes its own auto-update mechanism.

2 1

Newbie Port Creator Questions
by Jonathan Strine 04 Sep '07

04 Sep '07

All, I am working on creating ports for a few applications. I have created and submitted my first one just yesterday (libelf-0.8.9). I am now working on my second (dynamips-0.2.7), but have a few questions I'm hoping someone can answer (not all relating to just dynamips-0.2.7). 1) I have successfully created a variant of dynamips using pcap. The process was rather simple. However, I am debating the creation of a third variant. A third party developer has created a source code patch that extends a certain function of dynamips in a useful way. Is it appropriate to include such a third party modification as a variant to a port? 2) In the case above, the third party patch file is written to be applied from the directory above the source code (I think this would be called the work directory) and not from inside the dynamips-0.2.7 directory created when the tarball is extracted. The best I can figure is that the patching phase does apply the patch while in this source directory (dynamips-0.2.7) and not from the work directory. It is possible to make it apply the patch from the work directory so that I do not have to modify the third party patch file for this variant? 3) The third party patch is licensed under the GPLv2 license. Are there any general concerns that I should worry about in either case where I use the patch file as is or in the case where I modify it? 4) If I cannot patch from the work directory, is it considered OK to modify the third party patch file to support patching from inside the dynamips-0.2.7 directory? 5) What is the best practice to make sure that during all the steps I am only referencing libraries and dependencies from the macports system and not accidentally compiling against pre-installed system libraries? I have run "port -d install foo" and read through the output, but I want to double check that I am not missing anything. I realize the above questions may be somewhat basic, but I'm hoping that armed with the answers I can make some valuable contributions to the vast library of ports available. Thanks! -- Jonathan Strine PGP Key ID: 0x0A02201C

4 7

Missing tickets
by Randall Wood 04 Sep '07

04 Sep '07

I recently had a ticket that I was not being listed in Trac, #11903. Changing its priority from "Expected" to "Normal" solved the problem. I wonder how many other tickets have invalid priorities since the change in Trac priority values? 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."

2 1

Re: [28325] trunk/dports/graphics/wxWidgets-devel/Portfile
by Ryan Schmidt 04 Sep '07

04 Sep '07

On Aug 28, 2007, at 05:18, source_changes(a)macosforge.org wrote: > Revision: 28325 [snip] > @@ -66,7 +66,7 @@ > --enable-monolithic > > platform darwin 8 { > - configure.env-append CC=/usr/bin/gcc-4.0 CPP=/usr/bin/cpp-4.0 > CXX=/usr/bin/g++-4.0 > + configure.compiler gcc-4.0 > } > > set installtype release Why do we keep repeating these lines in so many portfiles? Why isn't "configure.compiler gcc-4.0" the default on darwin 8, and similarly, "configure.compiler gcc-3.3" the default on darwin 7?

7 16

Re: [28562] trunk/dports
by Weissmann Markus 03 Sep '07

03 Sep '07

Hey, thanks a lot for fixing my typos! That was really quick! :) -Markus On 03.09.2007, at 21:52, source_changes(a)macosforge.org wrote: > Revision 28562 Author ryandesign(a)macports.org Date 2007-09-03 > 12:52:23 -0700 (Mon, 03 Sep 2007) Log Message fix syntax errors > introduced in recent configure.env cleaning Modified Paths > trunk/dports/gnome/acme/Portfile > trunk/dports/gnome/mergeant/Portfile > trunk/dports/gnome/oregano/Portfile > trunk/dports/gnome/xchat-gnome/Portfile > trunk/dports/lang/swi-prolog-lite/Portfile > Diff > Modified: trunk/dports/gnome/acme/Portfile (28561 => 28562) --- > trunk/dports/gnome/acme/Portfile 2007-09-03 19:43:44 UTC (rev > 28561) +++ trunk/dports/gnome/acme/Portfile 2007-09-03 19:52:23 UTC > (rev 28562) @@ -16,5 +16,5 @@ checksums md5 > 0e4b240662a706d529757a86fe4bf0c5 depends_lib lib:libgnome-window- > settings:control-center use_bzip2 yes -configure.cppflaghs-append "- > L${prefix}/lib" +configure.cppflags-append "-L${prefix}/lib" > configure.cflags-append "-bind_at_load -no-cpp-precomp - > flat_namespace -undefined suppress" > Modified: trunk/dports/gnome/mergeant/Portfile (28561 => 28562) --- > trunk/dports/gnome/mergeant/Portfile 2007-09-03 19:43:44 UTC (rev > 28561) +++ trunk/dports/gnome/mergeant/Portfile 2007-09-03 19:52:23 > UTC (rev 28562) @@ -13,7 +13,7 @@ checksums md5 > 42a2f6778b81409db6cd1baa49663dca use_bzip2 yes depends_lib > lib:libgnomedb-2:libgnomedb -configure.cppflags-append "-L${prefix}/ > lib +configure.cppflags-append "-L${prefix}/lib" configure.cflags- > append "-I${prefix}/include" platform darwin 8 powerpc { > Modified: trunk/dports/gnome/oregano/Portfile (28561 => 28562) --- > trunk/dports/gnome/oregano/Portfile 2007-09-03 19:43:44 UTC (rev > 28561) +++ trunk/dports/gnome/oregano/Portfile 2007-09-03 19:52:23 > UTC (rev 28562) @@ -15,4 +15,4 @@ use_bzip2 yes configure.args -- > mandir=${prefix}/share/man configure.cppflags-append "-L${prefix}/ > lib" -configure.clfags-append "-no-cpp-precomp -flat_namespace - > undefined suppress" +configure.cflags-append "-no-cpp-precomp - > flat_namespace -undefined suppress" > Modified: trunk/dports/gnome/xchat-gnome/Portfile (28561 => 28562) > --- trunk/dports/gnome/xchat-gnome/Portfile 2007-09-03 19:43:44 UTC > (rev 28561) +++ trunk/dports/gnome/xchat-gnome/Portfile 2007-09-03 > 19:52:23 UTC (rev 28562) @@ -17,5 +17,5 @@ depends_lib bin:gnome- > session:gnome-session patchfiles patch_outbound.c > configure.cppflags-append "-L${prefix}/lib" -confgure.cflags-append > "-no-cpp-precomp -flat_namespace -undefined suppress" > +configure.cflags-append "-no-cpp-precomp -flat_namespace - > undefined suppress" configure.args --enable-gnomefe --disable-python > Modified: trunk/dports/lang/swi-prolog-lite/Portfile (28561 => > 28562) --- trunk/dports/lang/swi-prolog-lite/Portfile 2007-09-03 > 19:43:44 UTC (rev 28561) +++ trunk/dports/lang/swi-prolog-lite/ > Portfile 2007-09-03 19:52:23 UTC (rev 28562) @@ -30,7 +30,7 @@ > distname pl-${version} worksrcdir pl-${version}/src - > configure.cflas-append "-I${prefix}/include" +configure.cflags- > append "-I${prefix}/include" configure.env CIFLAGS="-I${prefix}/ > include" configure.args --mandir=/${prefix}/share/man \ > _______________________________________________ > macports-changes mailing list > macports-changes(a)lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-changes --- Markus W. Weissmann http://www.mweissmann.de/

2 3

Portfile Pillow Fight
by Anders F Björklund 03 Sep '07

03 Sep '07

I ran "port lint all", and color-coded up the results in a page: http://svn.macports.org/repository/macports/users/afb/lint.html.gz Results: 4191 total, 1089 "green", 2549 "yellow" ("?"), 553 "red" ("!") The green ones have no warnings or errors reported, the yellow have lint warnings only, and the red ones report fatal errors... If you want a special port, you can jump to the anchor directly: lint.html#MacPorts Then there is a link from that, to any errors/warnings reported: lint.html#MacPorts_details --anders PS. Most of the warnings are missing newlines / trailing whitespace. Warning: Line 4 should be a newline (after PortSystem) The errors mostly comes from the omission of required variables. Error: Missing required variable: platforms

2 3

zsh and zsh-devel
by N_Ox 03 Sep '07

03 Sep '07

Hello, zsh is now quite old and its maintainship has been dropped. I'm the current maintainer of zsh-devel and I think it does not deserve its -devel nature. Should we delete zsh and rename zsh-devel? Regards, -- Anthony Ramine, the infamous MacPorts Trac slave. nox(a)macports.org

4 5