February 2008 - macports-dev - lists.macosforge.org

unison and protocol breakage
by Vincent Lefevre 19 Feb '08

19 Feb '08

The unison port has recently been upgraded from 2.13 to 2.27. The problem is that the protocol has changed between these versions, and unison 2.13 can't talk to unison 2.27: http://trac.macosforge.org/projects/macports/ticket/14172 The only solution that can work in every case (because users may need to do synchronization with machines that only have 2.13 and machines that only have 2.27) is to install the two binaries: unison-2.13 and unison-2.27 (note: when executing the remote unison binary, unison can automatically add its main version number thanks to the addversionno option). So, I think that the best solution is to have a port for the old version unison 2.13 (BTW, this is what Debian does for the 2.9 version and will probably do for the 2.13 version), which installs only the unison-2.13 binary (alternatively, there could be a variant that installs a "unison" binary too for those who don't need unison 2.27). In this case, what should the name of the port be? unison-2.13? unison2.13? -- 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)

5 9

4500 ports! (was: [34234] trunk/dports/PortIndex)
by Ryan Schmidt 19 Feb '08

19 Feb '08

On Feb 18, 2008, at 14:49, dluke(a)macports.org wrote: > Revision: 34234 > http://trac.macosforge.org/projects/macports/changeset/34234 > Author: dluke(a)macports.org > Date: 2008-02-18 12:49:41 -0800 (Mon, 18 Feb 2008) > > Log Message: > ----------- > > Total number of ports parsed: 4500 > Ports successfully parsed: 4500 MILESTONE! :)

1 0

master_sites not required if fetch.type is svn
by Blair Zajac 18 Feb '08

18 Feb '08

Hi, I'm getting this lint warning: Error: Missing required variable: master_sites on a port using fetch.type svn. Is master_sites really required? Should lint not warn if fetch.type is svn or cvs? Blair -- Blair Zajac, Ph.D. CTO, OrcaWare Technologies <blair(a)orcaware.com> Subversion training, consulting and support http://www.orcaware.com/svn/

3 2

Re: [34218] trunk/dports/lang
by Ryan Schmidt 18 Feb '08

18 Feb '08

On Feb 18, 2008, at 03:13, erickt(a)macports.org wrote: > Revision: 34218 [snip here and several places below] > Added: trunk/dports/lang/llvm-gcc42/Portfile > +patchfiles patch-gcc_Makefile.in Patchfile names should end with ".diff"; see output of "port lint" > +post-destroot { > + cd ${destroot}${prefix} Please don't use the "cd" command. It does not exist in MacPorts trunk and will not exist in MacPorts 1.7.0 and later. > +platform darwin { > + post-extract { > + system "rm -rf ${workpath}/llvm-gcc${major}-${version}.source/ > libstdc++-v3" Wouldn't "file delete ..." have been sufficient in place of "system 'rm -rf ...'"? > +platform powerpc { > + set triple powerpc-apple-darwin8 > + > + configure.env-append TRIPLE=${triple} > + configure.post_args --build=${triple} --host=${triple} --target= > ${triple} > +} > + > +platform x86 { There is no such thing as "platform x86". If you want to target Intel machines, use "platform i386". > + set triple i686-apple-darwin8 > + > + configure.env-append TRIPLE=${triple} \ > + TARGETOPTIONS="--with-arch=nocona --with- > tune=generic" > + configure.post_args --build=${triple} --host=${triple} --target= > ${triple} > +} You may in fact want to use "platform darwin powerpc" and "platform darwin i386" since a triple including "apple" is probably only appropriate on darwin. In fact you may also want to factor out common code. Like this (untested): set triple apple-darwin8 platform darwin powerpc { set triple powerpc-${triple} } platform darwin i386 { set triple i686-${triple} configure.env-append TARGETOPTIONS="--with-arch=nocona --with- tune=generic" } platform darwin { pre-configure { configure.env-append TRIPLE=${triple} configure.post_args --build=${triple} --host=${triple} --target=$ {triple} } } Is a triple including "darwin8" appropriate on darwin 7 or darwin 9? (I don't know; I'm just asking.)

2 1

Re: [34202] trunk/dports/databases/mysql5-devel/Portfile
by Ryan Schmidt 18 Feb '08

18 Feb '08

On Feb 17, 2008, at 08:24, jwa(a)macports.org wrote: > Revision: 34202 > http://trac.macosforge.org/projects/macports/changeset/34202 > Author: jwa(a)macports.org > Date: 2008-02-17 06:24:27 -0800 (Sun, 17 Feb 2008) > > Log Message: > ----------- > lint clean trailing whitespace The whitespace on those lines was intentional and desired by me. Lint's warning in this case was erroneous, an error I have already corrected in trunk.

1 0

Re-requesting commit for 'lang/slime' 14136
by Mark Evenson 17 Feb '08

17 Feb '08

I maintain 'lang/slime' but do not have commit rights. Could someone please review the [Portfile attached to ticket 14136][1], and either provide feedback or commit it? Extensive commentary on the changes has been attached to this ticket. [1]: http://trac.macosforge.org/projects/macports/ticket/14136 Thanks, Mark <evenson(a)panix.com> -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."

1 0

variant cascade
by Thomas Reifferscheid 17 Feb '08

17 Feb '08

Will "port install tea +foo" build the port coffee +bar? Portfile tea: depends_lib port:coffee variant foo requires bar { } variant bar { } ====================== Portfile coffee: variant bar { } Kind regards Thomas

2 1

Can some kind committer please promote/comment on "emacs compiling on Leopard" ticket #13492
by Mark Evenson 17 Feb '08

17 Feb '08

The ticket for [Emacs build broken under Leopard][1] has been open for a month, complete with a patch and verified solution. Could kind soul please either commit this patch or respond with feedback as to what needs to be done? [1]: http://trac.macosforge.org/projects/macports/ticket/13942

1 0

Updating macports.conf
by Rainer Müller 17 Feb '08

17 Feb '08

Hello, Currently on selfupdate macports.conf is not updated in any way if it already existed. This "hides" new options from long time users. An up-to-date macports.conf provides a good overview over all options and contains short documentation lines. I have two proposals how this could be changed to make it more easy for users to follow HOWTOs and/or tutorials. 1) Add macports.conf.dist Place a file named macports.conf.dist right beside macports.conf. It would be the same file as the install process would have generated if no macports.conf file exists. Then the user can copy & paste new options over to macports.conf. Advantages: * Easy to implement Disadvantages: * User still has to do it him/herself. 2) Parse macports.conf and regenerate it Parse the existing macports.conf and rewrite it completely. This takes takes all options already present and writes a new macports.conf (by also keeping a backup). Advantages: * macports.conf is always up-to-date * Does not require work by user Disadvantages: * More work to implement this. * Users will loose their formatting or comments, if they customized it. Any comments on this appreciated. Rainer

5 6

Let's avoid using md5 as checksum
by js 17 Feb '08

17 Feb '08

Hi, As you know, MD5 has serious flaws (http://en.wikipedia.org/wiki/MD5) So recently I don't use it and even remove it when I found it in the checksum part of portfile. I thought dropping use of md5 in portfile would be nice. Any thought?

11 22