ftp.gnu.org compromise and resultant trashing of lots of files.
Why they haven't gotten things back into a proper state yet is an
entirely different question.
* 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)
list by bsd.port.mk insert anti foot-shooting device, which prevents
infinite fork loop when the user defines corresponding USE_XXX in global
make.conf, command line or environment.
Similar devices should probably be inserted into ports that might be inserted
into dependency list by others bsd.foo.mk files (bsd.ruby.mk, bsd.python.mk
and so on.)
since I'm doing most of the updating, and am working on a
port/Mk/bsd.<gnublah>.mk to move some cruft around.
Sponsored by: Mr. Smith and Mr. Wesson. :)
He says:
Update libtool to 1.3.3 and modify it's behaviour a bit. It now
behaves like a stock libtool unless we start sending one of three
flags:
--disable-ltlibs Don't install .la files
--release-suffix Add the release to the end of all the libs (like
GLib/GTK+)
--release-ignore Don't add the release to any libs.
PR: 13114
1. Add a -prefix arguement to libtool, to find where the installed
copies of ltconfig and ltmain.sh reside.
2. Don't install the .la files unless --install-ltlibs is passed to
ltconfig.
3. Don't force linking with -lc, and allow -?thread to be passed to
the linker.
4. Don't build static libs if not using version numbers (for
plugins).
5. Install instead of
lib${release}.a lib.a
lib${release}.so lib.so
lib${release}.so.${ver} lib${release}.so.${ver}
to support multi-release installations.
6. Change version to "1.3-freebsd-ports" so people know who to
blame.
7. Misc fixes.
PR: 11839
Submitted by: maintainer
