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.
This update updates mod_jk to 1.2.4 and optionally creates
an apache2 module, if APACHE_PORT is set to ${PORTSDIR}/www/apache2
As a separate PR, I send a new slave port that will hopefully
see to it that there's a package at your favourite package
site for both versions of apache.
PR: ports/56657
Submitted by: Palle Girgensohn <girgen@pingpong.net>
* 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)
has not been tested with Apache 2.0 though.
Looks for the right Tomcat JAR file. Since Tomcat 3.3
${TOMCAT_HOME}/lib/webserver.jar no longer exists.
Moved the file replacements (using ${SED}) from post-extract
to post-patch.
Changed the mod_jk.conf file to point to the right location
for the workers.properties file.
Bumped PORTREVISION.
Jakarta Tomcat 3.2.4 instead of 3.2.3. Cleaned the port
up a bit. It now also uses JDK 1.3.1 by default. This
behaviour can be changed by using the JAVA_PORT and the
JAVA_HOME parameters.
