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.
4.0.3:
- Leak in window manager's pixmap management
- Various file manager fixes
- Translation updates
- Support for KDE system tray was added
4.0.2:
* Improve window manager responsiveness
* Various bug fixes in file manager, window manager and panel
* More 64bit clean up
* New translation added: Azerbaijani
gettext and add it to LIB_DEPENDS.). [1]
- INSTALLS_SHLIB added to the Makefile (Only in case a library
get installed by the port.)
- remove NO_FILTER_SHLIB
- Replaced GNU_CONFIGURE with USE_LIBTOOL if INSTALLS_SHLIB was
set in the Makefile
- bump PORTREVISION
Noted By: Dinesh Nadarajah <dinesh_list@sbcglobal.net> [1]
