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

Number of commits found: 45

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 )

Conversion from (now defunct) autoconf-2.61 to autoconf-2.62

Tested by:      exp build run (erwin)

Update to the autotools new world order.

Tested by:      numerous package build runs
Approved by:    portmgr
Thanks to:      des, kris, linimon, pav

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

Remove USE_REINPLACE from all categories starting with D

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.

Minor INFO-related cleanups

Purge WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN

The versioned autotools are now strictly for building other ports in the tree.
Likewise, the gnu- autotools are for runtime dependencies for IDEs, and others,
where unmodified cross-platform capabilities are desired.

All that we see or seem, is but a dream, within a dream.

Take back maintainership.  I'll be scouring the PR database shortly,
if I miss any, or someone beats me to it, please feel free to reassign
appropriately.

- Don't hardcode versioned perl binary in shebang line, otherwise it will
  break on next perl update.

PR:             ports/81639
Submitted by:   Christopher Nehren <apeiron@coitusmentis.info>

. Change pre-install to pre-su-install since the target performs privileged
  operations.  This makes these ports installable by users other than root.

PR:             76422
Submitted by:   jhb

Relinquish maintainership.  I no longer have the time, energy,
or interest to look after these things any more.

To whomever picks these up, I salute you.  I'll reset the relevant
PRs to ports-bugs in a couple of weeks if no-one has taken over
maintainership.

Farewell, autotool hell.

Use INFO [1]
Other miscellaneous cleanups with info files

PR:             72651 [1]
Submitted by:   leeym [1]

Long-overdue cosmetic cleanups.

Somehow along the road, the MAINTAINER line got fat-fingered into
AINTAINER, with interesting consequences.

Fix missed patch, resulting in aclocal looking for itself in the wrong
place after the upgrade.

Submitted by:   marcus

Update to 1.4.6, the last of the 1.4.x automake branch.

Revert previous commit. We're still in freeze.

pointy hat: marcel

s/pre-install/pre-su-install/. Directories are being created.

Approved by: maintainer timeout.

Set some DEPRECATED and EXPIRATION_DATE knobs to indicate overall intention
of the autotools project to remove all but the latest versions of
libtool, autoconf, and automake, by 31st December 2004.

Note that autoconf259 and automake18 aren't yet accessible through the
relevant USE_* knobs, but will be as soon as bsd.autotools.mk comes into
existence.

Use the cosmetic BUILD_VERSION variable (a la libtool), switch portnames
away from using the version number twice.

Unbreak automake17, base on work from Rui Lopes <rui@ruilopes.com>

Assume maintainership as part of the whole "gnutools" integration process.

Please see http://freebsd.kde.org/memoriam/alane.php for an In Memoriam page.

        REST IN PEACE
        Alan Eldridge
Born December 15, 1961 in Iowa
Died June 6, 2003 in Denver, Colorado

Thank you for your contributions, you
will be greatly missed.

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

E Nomini Patri, E Fili, E Spiritu Sancti.

Use pre-everything:: instead of pre-everything: to avoid conflict with
targets in bsd.port.mk

change relative links to absolute

Remove "temporary" symlinks which could cause a build to fail.

Remove the StUdLyCaPs from maintainer name, 'cause some folks won't realize
mail's case insensitive and will try to type that. Sorry folks, purely a
cosmetic change here, nothing to see, move along, move along....

Changed MAINTAINER to my FreeBSD address.

Finally got enough diagnostic info. Fixes 44321. This is PORTREVISION=8,
folks.

PR:             44321

Rewrote installation procedure in Makefile since it wasn't quite right.
Hopefully fixed the PR listed.

PR:             44321
Submitted by:   parv

Removed erroneous ${DESTDIR} that I put in Makefile pre-/post- targets.

Updating portrevision, I said! DWIM!

1. Bumped portrevision (yes, again, sorry for the thrash).
2. Fixed bug that Knu pointed out, which was the bad dirs were captured
   in bsd.port.mk (to be fixed RSN, in testing now). Fixed with the magic
   of ... symlinks! (I always thought symlinks to . were lame, and they are,
   but sometimes they can get you out of a corner. Temporarily.)
3. The question is, will anything break trying to recursively go down the
   tree following symlinks? If so, that tool needs to be fixed. A symlink
   to '.' (or '..') just plain should not be followed.

Bottom line is, AUTOCONF_DIR, AUTOMAKE_DIR, & ACLOCAL_DIR work again.
As a side effect of this fix, you can now download the entire internet
onto 1 floppy disk.

Unbreak automake/aclocal from my changes this morning. My test case wasn't
thorough enough. PORTREVISION bump to force the change out (my judgement).

Cosmetic. Removed commented out stuff.

1. Made post-install DESTDIR-safe.
2. Made install put files in the RIGHT place (no extra level of dirs;
        changing 'datadir' is not the right thing to do).
3. Made nice exit when you have USE_AUTOMAKE* defined.
4. Renamed patch files so I can tell what they do.
5. Portrevision bump => 3.

1. Fixed the PR mentioned below, submitted by <below>.
2. perl -pi ==> ${REINPLACE_CMD}. Add USE_REINPLACE=yes.
3. @ some more Makefile commands so it doesn't talk quite so much.
4. Bumped PORTREVISION because of wanting to get Fix (1) out there.

PR:             42917
Submitted by:   "Greg 'groggy' Lehey" <grog@lemis.com>

Take maintainership since Ade Lovett departed and I know these programs
pretty well.

Due to popular demant into each port which might be inserted into dependency
list by bsd.port.mk insert anti foot-shooting device, which prevents
infinite fork loop when the user defines corresponding USE_XXX in global
make.conf, command line or environment.

Similar devices should probably be inserted into ports that might be inserted
into dependency list by others bsd.foo.mk files (bsd.ruby.mk, bsd.python.mk
and so on.)

Relinquish all my ports.

Stage a mini-coup, and borrow these ports from portmgr@ for a while,
since I'm doing most of the updating, and am working on a
port/Mk/bsd.<gnublah>.mk to move some cruft around.

Sponsored by:   Mr. Smith and Mr. Wesson. :)

Eliminate file conflicts with devel/automake
Add ${PREFIX}/libexec/automake14/* links

PR:             36077
Submitted by:   Alan Eldridge <ports@geeksrus.net>

This was repo copied from the 'automake' port to give us a legacy   version. 
automake14 can live beside the latest 'automake', and is invoked   specifically
as 'automake14'.    

Number of commits found: 45

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

^* - modified, not new

All vulnerabilities