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.
* kill devel/libtool and move to devel/libtool13, upgrading to 1.3.5
* upgrade repo-copied devel/libtool14 to 1.4.3
* break out libltdl into its own separate port
* move to version-numbered binaries/scripts (ie: there is *no* 'libtool'
any more -- USE_LIBTOOL and USE_LIBTOOL_VER are your friends)
Approved by: portmgr (kris) - for the bsd.port.mk hooks
Tested by: bento 4-exp builds (repeatedly)
for a buggy autoconf macro is included, so add USE_AUTOMAKE_VER and
USE_LIBTOOL (in this case, we need the libtool automake macro
AM_PROG_LIBTOOL).
PR: 36347
Submitted by: maintainer
- USE_AUTO* -> USE_AUTO*_VER=* where required
- USE_AUTO* / *_DEPENDS=.*auto*:*/devel/auto* -> GNU_CONFIGURE where OK
- Other minor changes to fix things
These changes should be no-ops with the current bsd.port.mk, but will
assist in preparing for the next generation of USE_AUTO*.
Submitted by: bento 4-exp USE_AUTO* cleanups
http://people.FreeBSD.org/~will/4-exp/http://bento.FreeBSD.org/errorlogs/4-exp-latest/
it is no longer required. Apologies to the various maintainers whom I
did not yet hear back from, but the ports freeze is coming up in a few
hours and I will be verifying all of these ports on a 4.1 machine
myself to catch any problems.
