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.
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.
Now try to use those variables everywhere around DIST* and PATCH*
definitions as far as possible, for ease of the future updates and the
neatness.
Okay, 60% of `japanese' ports have been done. :)
Avoid direct use of `/usr/local' in pkg/MESSAGE and use `${PREFIX}'
literally instead.
Indicated by: portlint
* Introducing `MESSAGE_SUB' might be a good idea to do substitutions
* in order to give proper instructions.
As the new version of esecanna has introduced dynamic module loading
mechanism, the port esecanna-vje30 has to be split into two ports
named esecanna and esecanna-module-vje30
PR: ports/16972
Submitted by: knu@idaemons.org
