Remove expired ports:
2018-12-19 net/py-libstorj: Broken for more than 6 months
2018-12-20 net/xferstats: Uses obsolete glib12
2018-12-20 net/wmlj: Uses obsolete glib12
2018-12-20 net/ipsorc: Uses obsolete glib12
2018-12-20 net/bsdproxy: Uses obsolete glib12
2018-12-20 net/gini: Uses obsolete glib12
2018-12-21 net/netatalk: Outdated branch of netatalk; use net/netatalk3 instead
2018-12-20 net/nocatsplash: Uses obsolete glib12
2018-12-20 net/jags: Uses obsolete glib12
2018-12-19 net/scribe: Broken for more than 6 months
2018-12-20 net/libnetdude: Uses obsolete glib12
2018-12-20 net/nepim: Uses obsolete glib12
2018-12-20 emulators/generator: Uses obsolete glib12
2018-12-19 emulators/py-nova: Broken for more than 6 months

Deprecate most glib12 consumers

With hat:	portmgr

Remove ${PORTSDIR}/ from dependencies, categories m, n, o, and p.

With hat:	portmgr
Sponsored by:	Absolight

- Unbreak installation on freebsd 9
- Drop DOCS option, it doesn't install anything

Remove empty directories to fix stage-qa

Cleanup plist

Replace USE_AUTOTOOLS=libltdl with an ordinary LIB_DEPENDS in all ports.
There are only 60 such ports so there doesn't need to be a separate
keyword or USES for this.

Approved by:	portmgr (bapt)

devel/glib12 x11-toolkits/gtk12:
- Convert to USES=libtool and bump dependent ports
- Add INSTALL_TARGET=install-strip
- Remove patches that renamed include directories and libraries so they
  didn't conflict with early development versions of glib/gtk 2.0

Add 4 new sed commands to USES=libtool.  The first two apply some of the
changes that Debian made to their libtool.  The first command applies to
libtool versions 1.4 and up.  The second command is somewhat more elaborate
but essentially it uses the sed hold space to move an "elif...fi" block
down.  It applies to 2.x.  Together these reduce overlinking to unpatched
.la files (from ports that don't have USES=libtool yet but also .la files
in the work directory).

The third and fourth command fix relinking.  During staging libtool may
relink libA when it links to another library in the work directory libB.
The reason is that libA created during build phase has its runpath set to
the location of libB in the work directory.  This allows running an
executable that links to libA from within the work directory.  The relink
removes this extra runpath.

- Convert to USES=libtool, drop .la files
- Fix DOCS installation
- Strip libraries
- Sort plist
- Fix comment
- Chase libpcapnav update

- Stage support

Fix properties on pkg-plist

Add NO_STAGE all over the place in preparation for the staging support (cat:
net)

Assign back to the pool.

Approved by:    maintainer via private mail

- Update to 0.12
- Remove PORTDOCS entries because docs are always disabled

PR:             ports/154719
Submitted by:   Armin Pirkovitsch <armin@frozen-zone.org>
Approved by:    maintainer timeout (3.5 months)

- Get Rid MD5 support

Sync to new bsd.autotools.mk

- Switch SourceForge ports to the new File Release System: categories starting
with N

-Repocopy devel/libtool15 -> libtool22 and libltdl15 -> libltdl22.
-Update libtool and libltdl to 2.2.6a.
-Remove devel/libtool15 and devel/libltdl15.
-Fix ports build with libtool22/libltdl22.
-Bump ports that depend on libltdl22 due to shared library version change.
-Explain what to do update in the UPDATING.

It has been tested with GNOME2, XFCE4, KDE3, KDE4 and other many wm/desktop
and applications in the runtime.

With help:      marcus and kwm
Pointyhat-exp:  a few times by pav
Tested by:      pgollucci, "Romain Tartière" <romain@blogreen.org>, and
                a few MarcusCom CVS users. Also, I might have missed a few.
Repocopy by:    marcus
Approved by:    portmgr

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

Fix the duplicate section.

Pointyhat to me.

Submitted by:   pointyhat via Erwin
Approved by:    garga (mentor)

Update netdude to 0.4.8a.
Update libnetdude to 0.10a.
Update libpcapnav to 0.8.

Pass maintainership to submitter.

PR:             ports/120116
Submitted by:   Brenton Chang <brenton.chang@gmail.com>
Approved by:    maintainer (implicit), garga (mentor)

Remove always-false/true conditions based on OSVERSION 500000

Update to 0.9

PR:             ports/107646
Submitted by:   Wesley Shields (maintainer)

- Update maintainer addresses

PR:             ports/102230
Submitted by:   Wesley Shields <wxs(at)atarininja.org>
Approved by:    krion (mentor)

- Update to 0.8
- Transfer maintainership

PR:             ports/96425
Submitted by:   Wesley Shields <wxs@csh.rit.edu>
Approved by:    Yann Berthier <yb@bashibuzuk.net> (maintainer)

Bump PORTREVISION on glib12/gtk12 consumer ports to ease the upgrade path.

Discussed with: kris
Approved by:    portmgr (implicit)

Conversion to a single libtool environment.

Approved by:    portmgr (kris)

SHA256ify

Approved by: krion@

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.

At Kris's request, back out the MACHINE_ARCH spelling correction until
after 5.4-RELEASE.

Assist getting more ports working on AMD64 by obeying the
Ports Collection documentation and use 'ARCH' rather than 'MACHINE_ARCH'.

Update maintainer's address

Submitted by: maintainer

Fix build with gcc-3.4

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

- Correct cutnpasto in Makefile header

PR:             ports/66429
Submitted by:   Wesley Shields <wxs@csh.rit.edu>

- Fix build on 4.x

Reported by:    kris
PR:             ports/66374
Submitted by:   Yann Berthier <yb@sainte-barbe.org> (maintainer)

Add libnetdude 0.6,

The core of the Netdude framework and the place where the
packet manipulations are performed. It allows you to implement
trace file manipulations at a much higher level of abstraction
than code written directly on top of the pcap library.

PR:             ports/66178
Submitted by:   Yann Berthier <yb@sainte-barbe.org>