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

Re: MacPorts 1.4.1 released for self update
by James Berry 17 Apr '07

17 Apr '07

Hi Dave, On Apr 16, 2007, at 2:57 PM, Dave Hill wrote: > In article <EF666B3B-1B9F-4C67-890A-92259A131643(a)macports.org>, > James Berry <jberry(a)macports.org> wrote: > >> MacPorts 1.4.1 has been released for selfupdate. It should hit the >> rsync servers within an hour or so. >> >> If you already have macports installed, simply "sudo port >> selfupdate". If you're doing a new install, install from the 1.4.0 >> disk image, then do a selfupdate. > > Doesn't work on 10.3.9. > > "sudo port -v selfupdate" ends with: > > checking for xml2-config... /usr/bin/xml2-config > checking for libxml >= 2.6.11... 2.6.16 > checking libxml/xmlwriter.h usability... no > checking libxml/xmlwriter.h presence... no > checking for libxml/xmlwriter.h... no > configure: error: Cannot build without libxml2 > configure: error: ./configure failed for src/programs/xar > > It's picking up the xml2-config from the BSD package which points > it at > /usr/include/libxml2/libxml - the contents of which come from the > DevSDK > package and don't include xmlwriter.h > > If I temporarily rename xml2-config out of the way it doesn't find the > one from dports, it just says it can't find xml2-config at all. > > Do I still have a functioning 1.4.0 install or am I hosed? Thanks for the report. Looks like we have problem building xar on Panther, due to a libxml2 library that is too old on panther. You should still have a functioning 1.4.0 system. You may type "port version" to verify. I'll probably put out a1.4.2 tonight that fixes this unless I can find another workaround. I think my solution will be to not build xar at all, for now. James.

2 1

Re: [24079] trunk/base/src/pextlib1.0/find.c
by Jordan K. Hubbard 17 Apr '07

17 Apr '07

On Apr 15, 2007, at 10:44 PM, source_changes(a)macosforge.org wrote: > Rewrite Pextlib find command. Now actually has useful API. Usage is > find ?-depth? ?-ignoreErrors? target ?target ...? varname body. - > depth identical to -d switch to find. -ignoreErrors causes it to > ignore permission/read errors. Does not follow symlinks. I'm not sure I exactly agree with that statement. First, the usage statement is a little confusing - can you cite some actually usage examples? Second, you've forced the execution of the body every time, and that was not the original intention of this API. The original intention was to have an Expr evaluated as a predicate and ONLY execute the body if the expr matched, allowing you to separate the "work statements" from the "match statements" - now you have to write a conditional into every body instead and it doesn't read as well. The fact that many people used find with an expr of "1" is besides the point - you could just as easily match against a specific filename regexp, or file type, or whatever. Just as find(1) has a whole bunch of predicates which precede -exec, so this command was intended to give you one complex predicate (with all the usual boolean operators) and the equivalent of "-exec" in the body. I'm having a hard time seeing this as anything but a regression, so perhaps you could explain your rewrite to the original author, at least? :-) - Jordan

3 6

MacPorts v1.4.2 released
by James Berry 17 Apr '07

17 Apr '07

MacPorts 1.4.2 has been released for selfupdate. It should hit the rsync servers in an hour or so. 1.4.2 is a minor bug fix release, cut quickly because 1.4.1 didn't build properly on panther (Mac OS X 10.3.x). ChangeLog entries: Release 1.4.2 (16-Apr-2007): - New logic for variants overload that basically yields to listing only variant +universal on ports that redefine it (pguyot in 24100). - Implement brand new fs-traverse command in Pextlib. See portfile.7 for documentation (eridius in r24079, r24080, and r24112). - Add per-user preferences in ~/.macports/user.conf. This will be used for submitter information. Simplify selection of ports.conf file: - ~/.portsrc is no longer supported. - Search order for ports.conf is now: - PORTSRC - ~/.macports/ports.conf - ${prefix}/etc/ports.conf Only the first file found will be parsed and used. (jberry r24071, r24113, r24114) - Improvements on livecheck: fixed a report bug, improved ruby group default behavior (pguyot in r24026 and r24018) - Remove xar from the build. xar doesn't build on panther due to a libxml2 lib too old for xar requirements. We'll find another way to deal with xar, perhaps by requiring users to install the xar port when they need its services. (jberry r24107:r24108) - Remove configure switch for building launchd support. (jberry r24107:r24108) - Remove compatibility upgrade for conf files from darwinports 1.1 to 1.2. (jberry r24106).

1 0

MacPorts 1.4.1 released for self update
by James Berry 16 Apr '07

16 Apr '07

MacPorts 1.4.1 has been released for selfupdate. It should hit the rsync servers within an hour or so. If you already have macports installed, simply "sudo port selfupdate". If you're doing a new install, install from the 1.4.0 disk image, then do a selfupdate. MacPorts 1.4.1 is a minor bugfix/feature release. ChangeLog entries include: Release 1.4.1 (14-Apr-2007): - Add responsive, reasonably fast http mirrors to openbsd group (pipping in r23343). - Resolved ticket #11637: livecheck incorrectly assumed that master_sites was set. (pguyot in r23329). - Add xar 1.4 into the build of MacPorts base. xar is now installed into /opt/local/, which will conflict with anybody who has the xar port installed. (jberry in r23687). - Add -I${prefix}/include -L${prefix}/lib to the default configure flags (pguyot in r23246 and r23291). - New options for configure flags (C|CPP|CXX|LD)FLAGS and logic to handle that and backward compatibility (pguyot in r23089, r23125, r23238, r23248 and r23249). - "port sync" now updates svn repos too (eridius in r22784). - Default +universal variant for configure-based ports (pguyot in r22313). - Fixed use of master_site in livecheck, added support for code.google.com checks, made the up to date message info (instead of debug) and improved debugging output with livecheck (eridius in r23888, r23889, r23890, r23894; pguyot in 23660) - Fixed a bug where running port test would not install dependencies when required. (pguyot in r23700) - New ruby portgroup option to specify the name of the module for gem-based ports. (pguyot in 23659) - New fetch option to ignore the SSL certificate when fetching from a secure site (default is to not ignore it). (pguyot in r23242) - Bugfix #11720. Fixes for variants.conf functionality. (jberry in r23967)

4 3

Re: sqlite3 errors?
by Daniel J. Luke 16 Apr '07

16 Apr '07

On Apr 16, 2007, at 4:33 PM, Avi Carmi wrote: > _tgetent referenced from libreadline expected to be defined in /opt/ > local/var/db/dports/build/ > _opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_ > dports_devel_ncurses/work/destroot/opt/local/lib/libncurses.5.dylib Your readline/ncurses are messed up. (mine were too, btw). This should fix it: sudo port clean --all readline ncurses sudo port -f uninstall readline ncurses sudo port install ncurses readline -- Daniel J. Luke +========================================================+ | *---------------- dluke(a)geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+

1 0

Re: [23968] trunk/base
by Ryan Schmidt 16 Apr '07

16 Apr '07

On Apr 13, 2007, at 22:34, source_changes(a)macosforge.org wrote: > Modified: trunk/base/doc/portfile.7 (23967 => 23968) > --- trunk/base/doc/portfile.7 2007-04-14 01:54:40 UTC (rev 23967) > +++ trunk/base/doc/portfile.7 2007-04-14 03:34:33 UTC (rev 23968) > @@ -1331,6 +1331,26 @@ > .br > .Sy Example: > .Dl default_variants +ssl +tcpd > +.It Ic unversal_variant > +When using MacPorts on MacOS X, a universal variant is defined and > +the default behavior is to configure ports with universal flags Wait... I thought the default behavior was for the +universal variant to be available to all ports, but that you had to select it if you wanted to use it.

2 6

Important: opendarwin imap users!
by James Berry 16 Apr '07

16 Apr '07

Those ex-opendarwin users who still utilize the opendarwin imap server should be aware that the opendarwin imap server will be shutting down sometime following a 10 day warning period from today. If you still utilize the opendarwin imap server, or if your @macports.org address forwards to that server, please make other arrangements to host your mail (hint: there are lots of free email services around, including gmail). If you do change the address to which your @macports.org address forwards, please notify kvv@apple to request that he change your email alias. Please let me know if you have any questions. James

1 0

Did someone bork eval_variants?
by Jordan K. Hubbard 16 Apr '07

16 Apr '07

I'm seeing this from any port and any operation, so it looks like something has gone south in ToT jkh@sam-> port -d -v livecheck DEBUG: Changing to port directory: . Can't map the URL 'file://.' to a port description file ("extra characters after close-quote"). Please verify that the directory and portfile syntax are correct. To use the current port, you must be in a port's directory. (you might also see this message if a pseudo-port such as outdated or installed expands to no ports). DEBUG: invalid command name "eval_variants" while executing "eval_variants variations livecheck" invoked from within "$workername eval eval_variants variations $target" (procedure "dportexec" line 7) invoked from within "dportexec $workername $target" Error: Unable to execute port: invalid command name "eval_variants"

3 11

Attention base developers: ChangeLog entries
by James Berry 16 Apr '07

16 Apr '07

A note for developers working on the MacPorts base code: - It is your responsibility to keep the ChangeLog up to date with substantive changes in base. - Not only does this tell users what has changed, but it also helps us internally track what has changed. - Changes that haven't been released should be put in the "unreleased" section of the ChangeLog file. These will be rolled into the proper release by the "releaser", who is a bit like the "decider" ;) - Please annotate ChangeLog entries with your name and the revision number when possible. Thanks! James

3 2

How can I determine if a function is available?
by Ryan Schmidt 16 Apr '07

16 Apr '07

I would like to improve the php5 port so that both an Apache 1 or 2 module and the FastCGI binary can be installed at the same time. The php build system does not accommodate targeting multiple SAPIs at once. Therefore it will be necessary to have port build once for the Apache module of choice, and then build again for the FastCGI module. I would like to make use of the strategy that was briefly employed by the zlib port to re-run the configure and build phases, but I need some advice, because of the following two commits: http://trac.macosforge.org/projects/macports/changeset/23238 http://trac.macosforge.org/projects/macports/changeset/23409 In r23238, the command "command" was removed, and a new command "command_exec" was introduced, but this change did not make it into MacPorts 1.4.0. In r23409, it was shown how this change will affect portfiles: a wrapper which called 'system "[command $cmd]"' was replaced with just "command_exec $cmd". So as I understand it, in MacPorts 1.4.0, I must use a wrapper which calls 'system "[command $cmd]"'. But whenever r23238 is merged into a released version of MacPorts (be that 1.4.1 or 1.5.0), this code will break, and it will then be necessary to use "command_exec $cmd". Is there a way that I can code my portfile today that will work with both current and future MacPorts versions? Is there a way that I can detect which of "command" or "command_exec" are available in the installed version of MacPorts? Thanks.

5 14