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

Number of commits found: 23

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 )

- Remove USE_GCC where it can be satisfied with base compiler on following
  FreeBSD versions: 5.3 and up, 6.x, 7.x, 8-CURRENT

- Welcome X.org 7.2 \o/.
- Set X11BASE to ${LOCALBASE} for recent ${OSVERSION}.
- Bump PORTREVISION for ports intalling files in ${X11BASE}.

Set USE_GCC=3.2+ to fix build on 4.x.

Reported by:    Chad R. Larson

- Update mail/spamprobe to 1.4d.
- Add an UPDATING entry to point out changes regarding the database backend(s).

Utilize USE_BDB.

PR:             107110
Submitted by:   leeym

Convert MAINTAINER to my freebsd.org account.

Drop USE_GCC: No longer necessary (reported by Mikhail Teterin)

PR:             ports/94094
Submitted by:   maintainer

- Update to 1.4b

PR:             93532
Submitted by:   maintainer

- Update to 1.4a

PR:             ports/92567
Submitted by:   maintainer

[PATCH] mail/spamprobe: update to 1.4, take maintainership

        - Update to 1.4
        - Take maintainership
        - Optionally depend on libungif
        - Remove local patch for gcc 2.x; instead, depend on gcc 3.2+ (untested
on 4.x -
          I hope it makes it work without any patches there).
        - Remove local patch for using OpenSSL's MD5 implementation.

        Removed file(s):
        - files/patch-md5
        - files/patch-strings

PR:             ports/91232
Submitted by:   Stefan Walter <sw@gegenunendlich.de>

- Update to 1.2a
- More download locations

PR:             ports/85343
Submitted by:   Stefan Walter <sw@gegenunendlich.de>

Update from 1.0a to 1.2. Fix to use OpenSSL's (optimized) md5 routines
instead of compiling the vendor's (as every other package seems to be
doing now) -- again.

Update to 1.0a

PR:             ports/82077
Submitted by:   ports fury

Remove 1-line plists in favour of PLIST_FILES

With portmgr hat on, reset maintainership of ports whose committer has
been inactive for more than 6 months and who has not responded to email
about his status.

Update to 0.9h.

Approved by:    maintainer timeout

Update to 0.8b

Clear moonlight beckons.
Requiem mors pacem pkg-comment,
And be calm ports tree.

E Nomini Patri, E Fili, E Spiritu Sancti.

Pass MAKE_ENV to post-build and post-install MAKE invocations to ensure
the things like PREFIX are correct. BTW, this software compiles/link
with db4 as well as db3 now, but the port unconditionally uses db3.

Update to 0.7c. Respect C(XX)FLAGS. The new version uses md5 checksums
to identify messages -- force it to use our -lmd instead of letting it
install the N+1st implementation. Use the tiny piece of sprint(3)
to convert the 16-byte digest into the printable 32-char string (the
wisdom of storing such a string instead of the raw digest discussed
with the author already).

Don't copy the manpage from FILESDIR -- compress and/or install it
directly from FILESDIR.

Approved by:    maintainer timeout

Update to 0.7a.
WARNING!  Database format has changed.  Rebuild required.

Spam detector using Bayesian analysis of word counts.

Number of commits found: 23

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

^* - modified, not new

All vulnerabilities