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.
the libtoolX ports instead of the one included with each port. Ports that
set USE_LIBTOOL_VER=X will now use the ports version of libtool instead of
the included version. To restore previous behavior, use the new macro,
USE_INC_LIBTOOL_VER. Both macros accept the same argument: a libtool version.
For example, to use the ports version of libtool-1.5, add the following to
your Makefile:
USE_LIBTOOL_VER= 15
To use the included version of libtool with extra hacks provided by
libtool-1.5, add the following to your Makefile:
USE_INC_LIBTOOL_VER= 15
With this change, ports that had to add additional libtool hacks to prevent
.la files from being installed or to fix certain threading issues can now
delete those hacks (after appropriate testing, of course).
PR: 63944
Based on work by:eik and marcus
Approved by: ade (autotools maintainer)
Tested by: kris on pointyhat
Bound to be hidden problems: You bet
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.
From: Motomichi Matsuzaki <mzaki@e-mail.ne.jp>
Subject: Re: question about FreeBSD ports you maintain
Briefly, I have no time for maintaining ports.
So I wish to leave the maintainer position of these ports:
biology/fastdnaml
textproc/wv
Thanks you for maintaining the FreeBSD system.
Best regards,
Motomichi Matsuzaki
When using 'portinstall wv' nothing is mention about depending
on lynx. however when using 'wvText' it mentions that it
can't find lynx so the text output will look bad.
PR: ports/45611
Submitted by: Nick Jennings <nkj@namodn.com>
Submitted by: KATO Tsuguru <tkato@prontomail.com>
Sorry to commit this before the MAINTAINER comments on the update, but
we need to fix this popular port as soon as possible which has been
broken for long.
PR: ports/30379
accordingly. This fixes the bogon where you could do a
pkg_delete on libwmf, and then have mswordview fail since
it was linked against shared libraries which had disappeared.
