- many minor changes inspired by apache13-modssl
(e. g. change datadir from ${PREFIX}/www to ${PREFIX}/share/apache)
- patches.modssl/ is not needed any longer (same patches for modssl and
non-modssl case)
is created, i. e. no additional support for e. g. databases
It is possible to build an apache13-php3 package now.
- honor ${CC} and ${CFLAGS} while compiling PHP3
- make apache13-php3 ${WRKDIRPREFIX} clean
- added OpenLDAP support
Requested by: Kurt D. Zeilenga <Kurt@OpenLDAP.Org>
- upgrade to mod_ssl-2.1.3
i. e. apache13-php3 supports SSL now!
- upgrade to Apache 1.3.2 and PHP 3.0.4
- enable track-vars for PHP3 by default to support phplib
(http://phplib.shonline.de/)
Pointed out by: Thomas Kuehne <thomas@todo.de>
- losts of minor changes (install php-icons, index.php3 as DirectoryIndex,
support .php3 and .phtml suffixes, enable application/x-httpd-php3-source
for .phps and .php3s, install default php3.ini-dist, ...)
Submitted by: Dirk Froemberg <ibex@physik.TU-Berlin.DE>
- change maintainer to Dirk Froemberg <ibex@physik.TU-Berlin.DE>, since
he is now the driving force
- totally revamped configuration (dialog based as in ghostscript)
- make portlint happy (andreas@FreeBSD.ORG), APACHE_VER and PHP3_VER
variable has to appear later in Makefile, not in front of DISTNAME
and PKGNAME
Submitted by: Dirk Froemberg <ibex@physik.TU-Berlin.DE>
- now based on apache 1.2.6 and PHP3 support with the tough help of Dirk
- Supports 3 kinds of databases now
- msql
- mysql
- postgresql
- Only modified order in Makefile to keep portlint happy
- Fixed php's configure section in Makefile, to use CC and CFLAGS from
/etc/makefile, instead to use -g -O2
- only one patches subdir remains
This port should now be "repository moved" from:
apache-php
to something like:
apache12-php3
Obtained from: Dirk Froemberg <ibex@physik.TU-Berlin.DE>
Currently 2 kind of databases will be supported, msql and mysql
The problem is, that depending on the flavour of database you want
to support, you need a different set of patches to apache's
Makefile, so that header and loader flags, paths and libs
are correctly resolved ...
I marked this port as BROKEN, since I wasn't able, to exactly
check the whole port due to the fact, that currently I only
have one db installed. Will try to get it managed next weekend.
Well if someone is so keen, then simply remove BROKEN and you
should be able to use what's already possible ...
on the presence of SECURE_SERVER.
2) Clean up the installation in accordance with BSD religion:
Now all the configs go in ${PREFIX}/etc/apache and the
data (documents) stay in ${PREFIX}/www.
