Bye bye abandonwares (part 3)

2011-08-01 deskutils/gkrellm-timers: No more public distfile
2011-08-01 deskutils/multi-backgrounds-daemon: Looks like an abandonware, no
more public distfile
2011-08-01 deskutils/py-tagfu: Looks like an abandonware, no more public
distfile
2011-08-01 deskutils/taskstep: Looks like an abandonware, no more public
distfile
2011-08-01 devel/c_c++_reference: No more public distfiles
2011-08-01 devel/libcoyotl: Looks like an abandonware, no more public distfile
2011-08-01 devel/libfs++: Looks like an abandonware, no more public distfile
2011-08-01 devel/mkmf: Looks like an abandonware, no more public distfile
2011-08-01 devel/p5-Include: No more public distfiles
2011-08-01 devel/rubygem-newgem: broken since 2010/09/22
2011-08-01 devel/tpg: Looks like an abandonware, no more public distfile
2011-08-01 games/amphetamine: Looks like an abandonware, no more public distfile
2011-08-01 games/anagramarama: Looks like an abandonware, no more public
distfile

Another bunch of deprecation: no more public distfiles and/or abandonware

Update MASTER_SITES and WWW
Remove MD5

Sync to new bsd.autotools.mk

-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

- Unbreak build is fine. (tested on i386/amd64)

PR:             117800
Submitted by:   Pietro Cerutti <gahr@gahr.ch>
Approved by:    portmgr (pav)

BROKEN with gcc 4.2

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

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

Remove USE_REINPLACE from all categories starting with D

Conversion to a single libtool environment.

Approved by:    portmgr (kris)

- Add some SHA256 checksums

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

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'.

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

Tidy up whitespace.

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.

SIZEify.

De-pkg-comment.

- Fix MASTER_SITES
- Support CXXFLAGS properly
- GNU_CONFIGURE -> USE_LIBTOOL

PR:             46591
Submitted by:   Ports Fury

Fix PORTCOMMENTs that were killing INDEX builds.

105 pointy hats to:     me
Approved by:            pat

add libfs++ 0.1.7
C++ library which provides a file_iterator class