devel/autoconf*: restructure to prepare for 2.71

- Rename autoconf 2.13 port directory, package, and command all to
  autoconf2.13 just like ports like perl and python.
- Let USES=autoreconf run gtkdocize if necessary.
- Rewrite autoconf-wrapper and rename it autoconf-switch to reflect
  better what it does.
- Delete patch-bison.  It has been reverted upstream.
- Add a patch to let autoreconf set the AUTOCONF environment variable
  so subprocesses like automake use the correct version.
- Make building of info files optional.
- Address portlint, portclippy, portfmt issues in devel/autoconf*.

PR:		259556, 263970

devel/autoconf213: Add NO_ARCH

Approved by:	portmgr (blanket)

Remove # $FreeBSD$ from Makefiles.

Install texinfo files (GNU info) into ${PREFIX}/share/info

After a discussion on the mailing list on moving manpages to
${PREFIX}/share/man for consistency with base where it is
installed in usr/share/man, it appeared the same should happen
to GNU info files which were installed under share in base and
not in ports.

Now texinfo is not in base on any of the supported version of FreeBSD
it is possible to proceed to this move and it is easier to do than
the manpage change.

Other benefit than consistency are less patching: all build tools but
cmake are expecting info files to be under share/info and cmake (patched here)
was having an exception for BSD so the patch makes FreeBSD case less
specific for them

Bump revision of all impacted ports

PR:		232907
exp-run by:	antoine
Differential Revision:	https://reviews.freebsd.org/D17816

- Add LICENSE
- Update WWW

Approved by:	portmgr blanket

Remove ${PORTSDIR}/ from dependencies, categories d, e, f, and g.

With hat:	portmgr
Sponsored by:	Absolight

Pick up autotools@ ports.

Approved by:	portmgr (bapt)

MASTER_SITES cleanup.

- Replace ${MASTER_SITE_FOO} with FOO.
- Merge MASTER_SITE_SUBDIR into MASTER_SITES when possible. (This means 99.9%
  of the time.)
- Remove occurrences of MASTER_SITE_LOCAL when no subdirectory was present and
  no hint of what it should be was present.
- Fix some logic.
- And generally, make things more simple and easy to understand.

While there, add magic values to the FESTIVAL, GENTOO, GIMP, GNUPG, QT and
SAMBA macros.

Also, replace some EXTRACT_SUFX occurences with USES=tar:*.

Checked by:	make fetch-urlall-list
With hat:	portmgr
Sponsored by:	Absolight

- Remove libtool hacks and patches that are now handled by USES=libtool
- Remove CONFIG_SHELL from CONFIGURE_ENV because bsd.port.mk handles that

Nuke some @dirrm from devel

Fix build without texinfo in base

Convert from USE_BZIP2 to USES=tar:bzip2

Support stage

Fix package name collision

Add NO_STAGE all over the place in preparation for the staging support (cat:
devel part 1)

- convert to the new perl5 framework
- trim Makefile header

Approved by:	portmgr (bapt@, blanket)

Tweak COMMENT lines to indicate the legacy nature of these two ports.

-remove MD5

Reassign the autotools-related ports to a new mailing list,
autotools@FreeBSD.org.  This is for individuals willing to put in
the hard work to generate patches and work with portmgr as we put
them through -exp runs and work through port breakage that they
create.  (A huge number of ports depend on these, so -exp runs are
required.)

Thanks to aDe@ for all the thankless work he's done over the years
to tame these beasts.

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

Handle an edge-case where lang/gawk is installed prior to any autoconf*
ports, which then results in an implicit dependency on gawk, with the
obvious bad things happening should gawk be later removed.

Note that because this is an edge case, which most folks will not run
into, and because it doesn't change the default package, I am not
bumping PORTREVISION as suggested in the original patch.

PR:     125101
Who:    matthias <dot> andree <at> gmx <dot> de

Large round of typo fixes in ports/devel (pkg-descr).

Update to the autotools new world order.

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

Add SHA256

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.

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

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.

Add SIZE to distinfo's

Prompted by:    trevor

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.

Point "legacy" autoconf distfile at ${MASTER_SITE_LOCAL}

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

Unbreak autoconf257, based on work from Rui Lopes <rui@ruilopes.com>

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

s,/bin/sh,${SH},.

Obtained from:  devel/autoconf

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

Add USE_PERL5.

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.

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

Set CONFIG_SHELL in env so always use /bin/sh. This way results are
at least (closer to) deterministic.

PR:             39492
Submitted by:   naddy

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.

1. Make nicer message is USE_AUTOCONF* defined.
2. Make post-install target actions DESTDIR-safe.

Portrevision => 3.
Put the damn support files in the right place. Modifying $(datadir) was
not the right way to do it. I knew there was something about this port that
bugged me. I am content now. Love is all you need. Give peace a chance.

Renamed patch files so I can tell what they do.
Changed $(INSTALL) to $(INSTALL_SCRIPT) in Makefile.in for the scripts.

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/autoconf
Add ${PREFIX}/libexec/autoconf213/* links

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

Bump PORTREVISION for including install-sh.  *sigh*    

Provide install-sh.    

Grrr. actually make it work post-repocopy.    

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