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

Re: [27772] trunk/dports/sysutils/logrotate/Portfile
by N_Ox 12 Nov '07

12 Nov '07

Le 14 août 07 à 06:57, source_changes(a)macosforge.org a écrit : > Revision 27772 Author markd(a)macports.org Date 2007-08-13 21:57:36 > -0700 (Mon, 13 Aug 2007) Log MessageMake port conform to mtree > standards properly.Modified Paths > trunk/dports/sysutils/logrotate/Portfile > Diff > <snip> > + xinstall -d ${destroot}${prefix}/share/man/man8 > + xinstall -m 755 ${worksrcpath}/logrotate.8 ${destroot}${prefix}/ > share/man/man8 > <snip> > _______________________________________________ > macports-changes mailing list > macports-changes(a)lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-changes By the way, manpage permissions should be 444, and as share/man/man8 is already in mtree, it is useless to install it beforehand. -- Anthony Ramine, the infamous MacPorts Trac slave. nox(a)macports.org

3 7

MacPorts should require the latest Xcode
by Ryan Schmidt 24 Oct '07

24 Oct '07

Here's a message from the -users list just now: On Jul 28, 2007, at 18:39, Chris Waterson wrote: > Hey, I had the same problem. It turns out I was using an older > version of Xtools (specifically, version 2.3). After upgrading to > Xtools 2.4.1, things worked fine. (The specific trouble, which you > can see if you get rid of the "-j2" option in the makefile, is that > they've changed some of the defines in the header files that the > boehm-gc needs.) Problems caused by old Xcode versions are reported by users with some regularity. I suppose we could add something to the FAQ, but users don't always read the FAQ, and the first step of the first section of the installation guide already reads: "Download and install the latest version of Xcode Tools—do not install an older version from the OS X 10.4 install disk or some ports may fail to install." We should not allow users to run into this problem. Can we please modify MacPorts base to issue a fatal error and refuse to do anything unless the latest Xcode (2.4.1 on 10.4.x, 1.5.x on 10.3.x) is installed? I think this would be a good idea. When new versions of Xcode are released, we can update base as needed.

5 6

[PATCH] wireshark Portfile change for SSL / TLS Decryption
by Jon Passki 12 Sep '07

12 Sep '07

Hey All, This patch will allow wireshark to decode SSL and TLS packets [1]. Tested with clean --all wireshark, configure, and install. Tested against test SSL data [2], decoded HTTP session. % port version Version: 1.520 [1] http://wiki.wireshark.org/SSL [2] http://wiki.wireshark.org/SampleCaptures?action=AttachFile&do=get&target=sn… --- Portfile.orig 2007-08-29 17:41:20.000000000 -0500 +++ Portfile 2007-08-29 17:41:01.000000000 -0500 @@ -27,7 +27,8 @@ port:gtk2 \ port:openssl \ port:libpcap \ - port:zlib + port:zlib \ + port:gnutls configure.args --enable-gtk2 \ --with-net-snmp=no --with-ucd-snmp=no \ @@ -37,6 +38,7 @@ --disable-ipv6 \ --with-pcap=${prefix} \ --with-ssl=${prefix} \ + --with-libgnutls-prefix=${prefix} \ --with-zlib=${prefix} \ --mandir=\\\${prefix}/share/man \ --infodir=\\\${prefix}/share/info \ [galt] ~% uuencode -m Portfile.patch Portfile.patch begin-base64 644 Portfile.patch LS0tIFBvcnRmaWxlLm9yaWcJMjAwNy0wOC0yOSAxNzo0MToyMC4wMDAwMDAwMDAgLTA1MDAKKysr IFBvcnRmaWxlCTIwMDctMDgtMjkgMTc6NDE6MDEuMDAwMDAwMDAwIC0wNTAwCkBAIC0yNyw3ICsy Nyw4IEBACiAJCXBvcnQ6Z3RrMiBcCiAJCXBvcnQ6b3BlbnNzbCBcCiAJCXBvcnQ6bGlicGNhcCBc Ci0JCXBvcnQ6emxpYgorCQlwb3J0OnpsaWIgXAorCQlwb3J0OmdudXRscwogCiBjb25maWd1cmUu YXJncwktLWVuYWJsZS1ndGsyIFwKIAkJLS13aXRoLW5ldC1zbm1wPW5vIC0td2l0aC11Y2Qtc25t cD1ubyBcCkBAIC0zNyw2ICszOCw3IEBACiAJCS0tZGlzYWJsZS1pcHY2IFwKIAkJLS13aXRoLXBj YXA9JHtwcmVmaXh9IFwKIAkJLS13aXRoLXNzbD0ke3ByZWZpeH0gXAorCQktLXdpdGgtbGliZ251 dGxzLXByZWZpeD0ke3ByZWZpeH0gXAogCQktLXdpdGgtemxpYj0ke3ByZWZpeH0gXAogCQktLW1h bmRpcj1cXFwke3ByZWZpeH0vc2hhcmUvbWFuIFwKIAkJLS1pbmZvZGlyPVxcXCR7cHJlZml4fS9z aGFyZS9pbmZvIFwK ==== -- Jon Passki, Partner The Hursk Group, LLC e. jon.passki(a)hursk.com o. 651/222.3020 "Obvia conspicimus, nubem pellente Mathesi." PGP: 1BB0 A946 927B 93C3 ED6A 0466 6692 6C2C 84BE 4122

3 2

Re: [28120] trunk/dports/lang/python24/Portfile
by Anders F Björklund 08 Sep '07

08 Sep '07

> Revision > 28120 > Author > raimue(a)macports.org > Date > 2007-08-21 06:41:55 -0700 (Tue, 21 Aug 2007) > > Log Message > lang/python24: > Don't install python binaries without version suffix. > Use new python_select to choose your version. > > Modified Paths > • trunk/dports/lang/python24/Portfile > > Diff > > Modified: trunk/dports/lang/python24/Portfile (28119 => 28120) > --- trunk/dports/lang/python24/Portfile 2007-08-21 13:40:27 UTC (rev > 28119) > +++ trunk/dports/lang/python24/Portfile 2007-08-21 13:41:55 UTC (rev > 28120) > @@ -93,6 +93,20 @@ > } > } > > + > +# delete symlinks without version suffix, use python_select instead > to choose version > +platform darwin { > + post-destroot { > + cd ${destroot}${prefix} > + file delete bin/python > + file delete bin/pythonw > + file delete bin/idle > + file delete bin/pydoc > + file delete bin/smtpd.py > + file rename share/man/man1/python.1 share/man/man1/python2.4.1 > + } > +} > + > platform puredarwin { > configure.args-delete > --enable-framework=${prefix}/Library/Frameworks > configure.args-append --disable-toolbox-glue --disable-framework This change will break ports that depends on "python24" and then try to use the "python" binary, either directly with #!/opt/local/bin/python or with e.g. #!/usr/bin/env python. Maybe those ports using port:python24 should be patched to use "python2.4" instead ? --anders

4 9

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

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

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

Binutils installation problem
by Chiara Sandionigi 03 Sep '07

03 Sep '07

Hi! I need to install GNU Binutils but I get the following error during installation cc: unrecognized option '-no-cpp-precomp' /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_b inutils/work/binutils-2.17/libiberty/fibheap.c: In function 'fibheap_union': /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_b inutils/work/binutils-2.17/libiberty/fibheap.c:151: warning: implicit declaration of function 'free' /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_b inutils/work/binutils-2.17/libiberty/fibheap.c: In function 'fibheap_delete_node': /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_b inutils/work/binutils-2.17/libiberty/fibheap.c:258: error: 'LONG_MIN' undeclared (first use in this function) /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_b inutils/work/binutils-2.17/libiberty/fibheap.c:258: error: (Each undeclared identifier is reported only once /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_b inutils/work/binutils-2.17/libiberty/fibheap.c:258: error: for each function it appears in.) /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_b inutils/work/binutils-2.17/libiberty/fibheap.c: In function 'fibheap_consolidate': /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_b inutils/work/binutils-2.17/libiberty/fibheap.c:360: warning: implicit declaration of function 'memset' /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_b inutils/work/binutils-2.17/libiberty/fibheap.c:360: warning: incompatible implicit declaration of built-in function 'memset' make[2]: *** [fibheap.o] Error 1 make[1]: *** [all-libiberty] Error 2 make: *** [all] Error 2 Error: Status 1 encountered during processing. Can somebody help me to solve this problem? Thanks Chiara

4 7

xfig
by Sebastian Sandersius 03 Sep '07

03 Sep '07

It seems that xfig crashes with macports now. I don't know if its the new beta version (3.2.5-alpha5) or if its something with macports, because it worked fine with darwin. Basically what happens is that if you to click on the 'File','Edit','View','Snap', or 'Help' tabs it pulls down a blank list and then crashes with this message in the portal: color = '#ffcccc' xfig3.2.5: SIGBUS signal trapped xfig: figure empty or not modified - exiting Abort trap - Sebastian

3 3

Features desirable for packaging
by Anders F Björklund 01 Sep '07

01 Sep '07

It has been mentioned before, so I thought I'd summarize what features that could benefit the packaging targets (I'm thinking primarily of the "rpm" target here of course, but I'm sure it'd help pkg and deb targets as well): 1) Config files We need a feature in the Portfile to mark which of the install files are configuration. These files will then be handled specially when doing installations/upgrades/removals, in that any existing modified configuration will *not* be overwritten. It could also be helpful for implementing a similar feature in the regular install/activate target too. Syntax could probably be similar to "destroot.keepdirs" 2) Sub-packages When building binary packages, having everything in a single port increases the size of package dependencies greatly. Usually one doesn't need the developer files, so there's a whole bunch of headers and whatnot undesirable. Splitting these off into a subpackage called "*-dev" (from DEB) or "*-devel" (this RPM naming is already taken in MP unfortunately) helps here. Not sure about syntax here. It needs to list the files. 3) More metadata Some metadata is currently missing from the Portfiles. It would be nice if these could be added with MacPorts 1.6, but it does require a major update since the older "port" won't understand any such new fields added to the syntax. Extracting changelogs from svn might be nice to include too, but is probably not required until it has been fully automated. a) License metadata (http://trac.macports.org/projects/macports/ticket/7493) Currently all ports have license "Unknown", no matter what the actual license used. Example portfile syntax: "license GPL" b) Noarch metadata (http://trac.macports.org/projects/macports/ticket/12206) Currently all ports have architecture "native", no matter what the actual arch is. Example portfile syntax: "noarch yes" Neither of these are showstoppers for binary packages, but they would definitely improve the quality of them. Especially the "avoid deleting user preferences" and "don't require developer tools" I would consider rather essential... I'm sure we'll have some more concrete feedback when the first MacPorts 1.5 packaging run completes. Hopefully that'll be in time for sfiera's/jmpp's redesign of the webpage/database. Tentatively http://macports.org/packages/ --anders

3 3