devel/autoconf267

Bump autoconf 2.67->2.68 -- will deal with any fallout.

Fix mangled commit - no, I have no idea why this happened.

Autotools update.   Read ports/UPDATING 20100915 for details.

Approved by:	portmgr (for Mk/bsd.port.mk part)
Tested by:	Multiple -exp runs

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
 - Remove CONFIGURE_TARGET hack in various bsd.*.mk
 - USE_GNOME=gnometarget is now an no-op

Changes to individual ports, other than removing the CONFIGURE_TARGET hack:

= pkg-plist changed (due to the ugly CONFIGURE_TARGET prefix in * executables)
  - comms/gnuradio
  - science/abinit
  - science/elmer-fem
  - science/elmer-matc
  - science/elmer-meshgen2d
  - science/elmerfront
  - science/elmerpost

= use x86_64 as ARCH
  - devel/g-wrap

= other changes
  - print/magicfilter
    GNU_CONFIGURE -> HAS_CONFIGURE since it's not generated by autoconf

Total # of ports modified:  1,027
Total # of ports affected: ~7,000 (set GNU_CONFIGURE to yes)

PR:		126524 (obsoletes 52917)
Submitted by:	rafan
Tested on:	two pointyhat 7-amd64 exp runs (by pav)
Approved by:	portmgr (pav)

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

Tested by:	exp build run (erwin)

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

Missed patch.  Sigh.

Fix missed comment update

Introduce autoconf 2.62, which can now be used by other ports with the appropriate USE_AUTOTOOLS stanza.

Note that the mass-conversion from autoconf 2.61 -> 2.62 will take place
at a later date.

Remove autoconf-2.53/autoconf-2.59 from the tree, no longer needed.

PR:		116639

Cosmetic fix for manpages.  Correctly use -2.61 for references.

Submitted by:	Jan Henrisk Sylvester <me@janh.de> and others

Fix automake-1.10 and autoconf-2.61 correctly.

One bad merge out of 25.  Sigh.

Update to the autotools new world order.

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

- Set --mandir and --infodir in CONFIGURE_ARGS if the configure script   supports them.  This is determined by running ``configure --help'' in   do-configure target and set the shell variable _LATE_CONFIGURE_ARGS   which is then passed to CONFIGURE_ARGS. - Remove --mandir and --infodir in ports' Makefile where applicable   Few ports use REINPLACE_CMD to achieve the same effect, remove them too. - 

PR:		ports/111470
Approved by:	portmgr
Discussed with:	stas (Mk/*), gerald (info related stuffs)
Tested by:	pointyhat exp run

Put autoconf-2.61 into its correct location after repocopy

Say hello to autoconf-2.6.1 after repository copy from autoconf259

Remove USE_REINPLACE from all categories starting with D

Add SHA256

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.

Move devel/autoconf->devel/autoconf253 and devel/automake->devel/automake15 All autotools ports are now truly versioned and do not conflict with each other.

This marks the end of "Phase 1" of the autotools updates.

Actually put in relevant symlinks to the versioned files in ${PREFIX}/bin to non-versioned files in ${PREFIX}/libexec/<autotool><ver> so that the PATH magic in bsd.autotools.mk works correctly.

Fix for auto-creation of an auxiliary directory when using the base version of perl in 4.x

Whilst the package list isn't affected, PORTREVISION has been bumped
to warn 4.x users -- those on 5.x don't necessarily have to update.

PR:		68509
Submitted by:	Martin Kammerhofer <dada@pluto.tugraz.at>

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.

Say hello to autoconf 2.59 and automake 1.8(.3) after repo-copy. It's likely to be a really bad idea to use these until they're hooked into the new bsd.autotools.mk

Other minor cosmetic changes to COMMENT

Hackery after repo-copies from devel/autoconf and devel/automake respectively to make these true versioned ports

Bump PORTREVISION on all ports that depend on gettext to aid with upgrading.

(Part 2)

Add missing = at MASTER_SITES Noticed by: Subject: INDEX build failed

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>

Unbreak autoconf257.

Approved by:	ade

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

Fix dependency on running perl5 and s,/bin/sh,${SH},.

Pointed out by:	simokawa

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

comment out include of manpages.mk so wont break INDEX

mark BORKED until finished

starting work on actual port; this commit removes files from a previous version

Correct ports that were abusing the FORBIDDEN variable and replace with either IGNORE or BROKEN.

Since there seems to be some confusion, for the record:

BROKEN		is reserved for ports that don't work.  This will prevent
		users from installing the port, but please note that
		ports marked as BROKEN will still be built by bento
IGNORE		is reserved for ports that should not be built for one
		reason or another (including bento).  Users and bento
		will not build ports marked as IGNORE.
FORBIDDEN	is reserved for security breakages only!!!  Only mark a
		port as FORBIDDEN if there is a security issue with the
		port at the time.

Reviewed by:	kris (portmgr)

Put the MD5 back. Didn't mean to nuke it.

Add explicit ignore assignments to try to get bento to leave this shit alone.