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

Number of commits found: 51

- Fix build qt3 GUI while qt4.4 installed

PR:             126645
Submitted by:   "Dima Panov" <fluffy at fluffy dot khv dot ru>

- Install MySQL sample configuration files in EXAMPLESDIR.
- Add pkg-message to let the user know about the example configuration files
  and how to use them.
- Bump PORTREVISION.
- Restrict CONFLICTS as portlint(1) suggests.
- Clean up.

PR:             ports/113538
Submitted by:   "User1001" <supraexpress@globaleyes.net>
Reworked by:    alepulver (myself)

Don't install world writeable files and directories.

PR:             114286
Reported by:    "O. Hartmann" <ohartman@zedat.fu-berlin.de>

Don't clobber config files on update.

PR:             111923
Submitted by:   emaste

- Fix the build if MiniSQL headers are present: never build MiniSQL
ODBC driver. It is not in our pkg-plist and the build is broken.
- Bump PORTREVISION.

Do not call ${CHOWN} if INSTALL_AS_USER is set.

- Update to 2.2.12

PR:             ports/105029
Submitted by:   KATO Tsuguru <tkato432@yahoo.com>
Sponsored by:   FreeBSD Bug-a-thon #2

- s,INSTALLS_SHLIB,USE_LDCONFIG,g
- these include comms/ converters/ databases/ devel/ 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.

- update to 2.2.11

PR:             78874
Submitted by:   Ports Fury

Update to version 2.2.10

PR:             ports/73347
Submitted by:   Ports Fury

Apply a big libtool patch to allow porters to use the libtool installed by
the libtoolX ports instead of the one included with each port.  Ports that
set USE_LIBTOOL_VER=X will now use the ports version of libtool instead of
the included version.  To restore previous behavior, use the new macro,
USE_INC_LIBTOOL_VER.  Both macros accept the same argument: a libtool version.

For example, to use the ports version of libtool-1.5, add the following to
your Makefile:

USE_LIBTOOL_VER=        15

To use the included version of libtool with extra hacks provided by
libtool-1.5, add the following to your Makefile:

USE_INC_LIBTOOL_VER=    15

With this change, ports that had to add additional libtool hacks to prevent
.la files from being installed or to fix certain threading issues can now
delete those hacks (after appropriate testing, of course).

PR:             63944
Based on work by:eik and marcus
Approved by:    ade (autotools maintainer)
Tested by:      kris on pointyhat
Bound to be hidden problems:    You bet

Build with thread supports by default.
Bump PORTREVISION.

Update to version 2.2.9

PR:             ports/68370
Submitted by:   Ports Fury

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 version 2.2.8

PR:             ports/63132
Submitted by:   Ports Fury

- Add CONFLICTS between libiodbc and unixODBC

PR:             ports/62528
Submitted by:   Ports Fury

- Fix a bug in 2.2.7 that will send a statement to the
  incorrect state if SQLMoreResults is used

PR:             61421
Submitted by:   Ports Fury

- Update to version 2.2.7

PR:             60007
Submitted by:   Ports Fury

Update to version 2.2.6

PR:             54800
Submitted by:   KATO Tsuguru <tkato@prontomail.com>
Approved by:    fjoe (mentor) (implicit)

Update to 2.2.5.

PR:             ports/51361
Submitted by:   Ports Fury

De-pkg-comment.

Update to 2.2.4

PR:             47484
Submitted by:   KATO Tsuguru <tkato@prontomail.com>

support qt3

PR:             43695
Submitted by:   Ports Fury

Update to 2.2.3

PR:             42033
Submitted by:   tkato@prontomail.com

upgrade to 2.2.2

PR:             40357
Submitted by:   Ports Fury

Update to 2.2.1.

PR:             37836
Submitted by:   KATO Tsuguru <tkato@prontomail.com>

Update to 2.2.0    

Update to 2.1.1    

upgrade to 2.1.0    

Upgrade to 2.0.9    

Update to 2.0.8.    

Build with --enable-threads=no by default to get around the libc_r   weirdness. 
  

Update to 2.0.7.    

Update to version 2.0.5    

Upgrade to version 2.0.4    

- Add missing file (bin/isql) to pkg-plist   - Use NOPORTDOCS PLIST_SUB    

Update to 2.0.3    

Update to 2.0.2    

Update to 2.0.0    

Update to version 1.8.13    

Ditch out "Version required" from comments section.    

There has got to be someone who understands databases better than me to shepard 
 this port. :-)    

Oops. Somehow an extra USE_XLIB got into the !WITH_X case.    

Add USE_LIBTOOL to fix c_r issues.    

Rename INSTALLS_SHLIBS to INSTALLS_SHLIB.  (There was a typo in the   previous
commit message to bsd.port.mk, which said INSTALL_SHLIBS.  Boo.)    

Fix MASSIVE typo INSTALL_SHLIBS --> INSTALLS_SHLIBS, which occured because I  
just cun'n'pasted the name from Satoshi's commit message without checking   it. 
  

First round of INSTALL_SHLIB fixes.    

Make the port work in the absence of X    

Specify the path to javac just in case it is not in the user's PATH as   it
wasn't on bento.    

Number of commits found: 51

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

^* - modified, not new

All vulnerabilities