A ports freeze means that commits will be few and far between and only by approval.

Number of commits found: 10

Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.
Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.

To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.

To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.

Changes to Mk/*:
 - Add runtime detection magic in bsd.port.mk

(Only the first 15 lines of the commit message are shown above )

Use libtool port instead of included version to avoid objformat a.out botch

- s,INSTALLS_SHLIB,USE_LDCONFIG,g
- these include irc/ japanese/ java/ lang/ mail/ math/ maintained by ports@

PR:             ports/101916
Submitted by:   Gea-Suan Lin <gslin_AT_gslin dot org>

Conversion to a single libtool environment.

Approved by:    portmgr (kris)

Mass-conversion to the USE_AUTOTOOLS New World Order.  The code present
in bsd.autotools.mk essentially makes this a no-op given that all the
old variables set a USE_AUTOTOOLS_COMPAT variable, which is parsed in
exactly the same way as USE_AUTOTOOLS itself.

Moreover, USE_AUTOTOOLS has already been extensively tested by the GNOME
team -- all GNOME 2.12.x ports use it.

Preliminary documentation can be found at:
        http://people.FreeBSD.org/~ade/autotools.txt

which is in the process of being SGMLized before introduction into the
Porters Handbook.

Light blue touch-paper.  Run.

change the libtool version to use from 1.3 to 1.5

Clean up time for email addresses MIA!
If you know new email addresses for the people involved, please send-pr it!

<mcsi@agava.com>: host relay.agava.net.ru[195.161.118.3] said: 550
    <mcsi@agava.com>: User unknown in local recipient table (in reply to RCPT
    TO command)

<woju@bbsmail.ntu.edu.tw> (expanded from <woju@bbsmail>): Host or domain name
    not found. Name service error for name=bbsmail.ntu.edu.tw type=A: Host not
    found

<esoha@attbi.com>: host gateway.attbi.com[204.127.198.6] said: 551 not our
    customer (in reply to RCPT TO command)

<crow@nektor.hu>: host mail.kapu.hu[195.70.32.236] said: 550 unknown user (in

(Only the first 15 lines of the commit message are shown above )

Whoa there, boy, that's a mighty big commit y'all have there...

Begin autotools sanitization sequence by requiring ports to explicitly
specify which version of {libtool,autoconf,automake} they need, erasing
the concept of a "system default".

For ports-in-waiting:

        USE_LIBTOOL=YES         ->      USE_LIBTOOL_VER=13
        USE_AUTOCONF=YES        ->      USE_AUTOCONF_VER=213
        USE_AUTOMAKE=YES        ->      USE_AUTOMAKE_VER=14

Ports attempting to use the old style system after June 1st 2004 will be
sorely disappointed.

Update to 1.4.7

PR: 50689
Submitted by: MAINTAINER

New ports: mail/jamlib

        These are a collection of subroutines that encapsulate much
        of the format-specific and tedious details of the JAM message
        base format.  The idea is that application programmers by
        using these routines can concentrate on the more high-level
        issues of their programs instead of worrying about their
        JAM routines.

PR:             ports/45467
Submitted by:   Cyril Margorin <cyrilm@immo.ru>

Number of commits found: 10

14 vulnerabilities affecting 30 ports have been reported in the past 14 days

^* - modified, not new

All vulnerabilities