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.
Committers: Please be careful to not carelessly remove libtool archives
from ports in KDE's dependency path. You will very likely cause much pain
for users in the process.
Discussed with: bland
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.
so that SGI can integrate them, along with the rest of the current patches,
into its own tree. The BSD license on the old code was preventing that,
as SGI's legal weasels will only allow them to accept GPL'd code.
My stuff's more well written anyway; I know how to write C++, the old author
didn't.
could without licensing problems. The rest they host as a separate patch on
their ftp server.
Please test this for compilation problems on -CURRENT with gcc-3.2.
- 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/
