From owner-freebsd-ports  Mon May 15  5:36:12 2000
Delivered-To: freebsd-ports@freebsd.org
Received: from privatecube.privatelabs.com (privatecube.privatelabs.com [198.143.31.30])
	by hub.freebsd.org (Postfix) with ESMTP id 20C9037B6F9
	for <FreeBSD-Ports@freebsd.org>; Mon, 15 May 2000 05:36:00 -0700 (PDT)
	(envelope-from mi@privatelabs.com)
Received: from misha.privatelabs.com (root@misha.privatelabs.com [198.143.31.6])
	by privatecube.privatelabs.com (8.9.2/8.9.2) with ESMTP id HAA24364;
	Mon, 15 May 2000 07:34:56 -0400 (EDT)
Received: from privatelabs.com (mi@localhost [127.0.0.1])
	by misha.privatelabs.com (8.9.3/8.9.3) with ESMTP id IAA52674;
	Mon, 15 May 2000 08:35:33 -0400 (EDT)
	(envelope-from mi@privatelabs.com)
From: mi@privatelabs.com
Message-Id: <200005151235.IAA52674@misha.privatelabs.com>
Date: Mon, 15 May 2000 08:35:32 -0400 (EDT)
Subject: Re: Apache & Module Port Status
To: "Scot W. Hetzel" <hetzels@westbend.net>
Cc: FreeBSD-Ports@freebsd.org
In-Reply-To: <005a01bfbd51$8af9f1a0$8dfee0d1@westbend.net>
MIME-Version: 1.0
Content-Type: TEXT/plain; CHARSET=US-ASCII
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

I always wanted to be able to add/remove modules without rebuilging
the server. May be, a new ports subtree is due -- /usr/ports/apache?

	-mi

On 13 May, Scot W. Hetzel wrote:
= I have done some more work on these ports, and now have the following
= building:
= 
= New port          Old port
= --------------    --------------
= apache13-base
= apache13
= apache13+ipv6
=     - need port maintainer to check how I fixed the IPv6 patch to co-exist
= with the EAPI patches
= 
= (ftp://www.westbend.net/pub/kame/misc/apache+eapi-1.3.12-v6-20000309a.diff.g
= z)
=         (replaced patches for http_main.c, and proxy_http.c due to conflict)
= 
= apache13-ssl
=     + preliminary SSL configuration info added to httpd.conf-dist (needs to
= be checked)
= 
= All apache13* ports now use the same layout (FreeBSD.layout).
= 
= mod_dav
= mod_dtcl
= mod_frontpage     apache13-fp
= mod_jserv         apache-jserv
= mod_php3          apache13-php3
=     + added support for mod_dav (needs testing)
= 
= mod_php4          apache13-php4
=     - needs upgrade to RC2
=     + added support for mod_dav (needs testing)
= 
= mod_ssl           apache13-modssl
=     - still needs a way to build a certificate
= 
= Could the maintainers of these ports check them out.
= 
= The ports are available from:
= http://www.westbend.net/~hetzels/mod_apache13.tgz
= 
= I think they are almost ready to be submitted but I thought I would get your
= opinions/changes first.
= 
= Scot.
= 
= P.S.  Listed below are a few things that still need to be accomplished.
= 
= It might be possible to combine the apache13 & apache13+ipv6 ports into one
= port, as the apache13+ipv6 port can be built with IPv6 support disabled.
= This still needs to be tested on 3-Stable.
= 
= If the above works for the apache13 port, then we might want to see if we
= can get the IPv6 patch to work with apache13-ssl in a similar manner.
= 
= We also need to check the Apache modules to see if they will work in an IPv6
= environment.
= 
= mod_php3 - add IPv6 Support
=     - ftp://ftp.kame.net/pub/kame/misc/php-307-v6-19990418.diff.gz
=         (NOTE: Patch mentions that it will not work on a non-IPv6 system due
= to missing functions).
= 
= mod_php4 - add IPv6 Support
=     - no patch available(Is one required?).
= 
= mod_frontpage - IPv6 Ready
=     - doesn't do anything with the IP addresses
=     (Don't know if the client will work because I have no IPv6 stack for
= Windows).
= 
= mod_ssl  - check if IPv6 Support is needed
= 
= mod_dav - check if IPv6 Support is needed
= 
= mod_jserv - check if IPv6 Support is needed
= 
= mod_dtcl - check if IPv6 Support is needed




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message