- move MASTER_SITES for mod_ssl from scripts/configure.php to Makefile
thus include them in the heavy rotation
- use ${PHP_DISTDIR} for PHP to minimize the diffs between apache13-php[34]
- cut down to 30 sites (10 for apache, php and mod_ssl each)
s/php3/php/g;
whereever appropriate.
This was done in preparation for a repository copy to apache13-php4
to keep the diffs between apache13-php3 and apache13-php4 as small as
possible.
[Has anyone figured-out what makes the number 393 so interesting to PW, now?]
I wonder what was going through Jordan's head during his infamous
$Id$-smashing commit.
Before I forget....
Thanks to naddy@mips.rhein-neckar.de (Christian Weisgerber) for prompting
this commit. See msg-id: 7geokh$tje$1@mips.rhein-neckar.de
- 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)
were alternated so the user does not have to get 10 apache MASTER_SITEs when all
they need is one 'mod' MASTER_SITE, which is what would happen if we used a
MASTER_SITE_APACHE or added all of the mirrors in a row.
Approved By: apache maintainers, asami
Submitted By: Brian Feldman <green@unixhelp.org>, billf
${MACHINE_ARCH}--freebsd${OSREL} is now passed to CONFIGURE_ARGS if
GNU_CONFIGURE is defined. Take the target out of CONFIGURE_ARGS of
some ports that added it explicitly; define it as
${MACHINE_ARCH}--freebsd if the port doesn't like the ${OSREL} part;
define it as something else (such as ${MACHINE_ARCH}--freebsdelf if
the port requires that; define it as an empty string if the port
doesn't like it at all.
The last might be a sign that a GNU_CONFIGURE port actually doesn't
use GNU's version of configure at all; but I don't have time to go
look at them all, we'll fix them as time goes on.
At least we've got much fewer "-unknown-"s in the tree as the result. :)
The default is mysql322 now, but take mysql321 if it is installed.
(mysql321 installs a static libmysqlclient.a only, mysql322 installs a
static and shared version of the library. Note that the build dependency
to mysql321 is a no op actually. It is in there to improve understanding(?).)
if the file or symlink exists already.
Reported by: Peter Hawkins <thepish@freebsd.org> (a long time ago...)
PR: ports/9347
Submitted by: Sheldon Hearn <axl@iafrica.com>
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>
Included freetype support for php
Why freetype support ?
If you compile PHP with gd and freetype[it's already a port], and grab
some free truetype fonts from microsoft in self-install.exe format you
can generate really nice on the fly gif's with text in them. Buttons,
banners etc.
William told me: I had to install the free microsoft fonts on my pc
and then ftp them. I can't think of a way to extract the files from
the .exe archive. I don't think it's a zip type.
I got the fonts microsoft link by digging around in
http://www.freetype.org
Submitted by: William Lloyd <wlloyd@mpd.ca>
fixes regarding compilation/linking with libgd
a fix for me in Makefile to make this submission $PREFIX clean
big thanks to William
Submitted by: William Lloyd <wlloyd@tolstoy.mpd.ca>
- 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>
New features:
- You have to set variable PHP_DBTYPE to msql or mysql by typing
make PHP_DBTYPE=[ msql | mysql ]
to build the port with msql or mysql support.
- The php configuration isn't interactive anymore
Theoretically we could default to mysql database and build
a package, so that make batch could work !
- Cleaned up port dependency, so that libgd actually gets build
(I fixed this one)
- made portlint as happy as I could, changed /usr/local to ${PREFIX}
and changed sed -> ${SED}
The only thing that is missing now is an apache-php-SSL port and
postgresql support ;-))
Submitted by: 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.
Remove pst's address from MAINTAINER, I don't know if any script
will fail if we have two addresses here so I don't want to risk
breaking something right before the release.
