From owner-freebsd-ports Tue Apr 11 17:14:57 2000 Delivered-To: freebsd-ports@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 4AFC737BA15; Tue, 11 Apr 2000 17:14:51 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id UAA04208; Tue, 11 Apr 2000 20:14:04 -0400 (EDT) Date: Tue, 11 Apr 2000 20:14:03 -0400 (EDT) From: "Matthew N. Dodd" To: Ben Laurie Cc: Dirk Froemberg , Adam Laurie , "David O'Brien" , greg@greg.rim.or.jp, sumikawa@FreeBSD.ORG, hetzels@westbend.net, rse@engelschall.com, ache@FreeBSD.ORG, winter@FreeBSD.ORG, ports@FreeBSD.ORG, asami@FreeBSD.ORG Subject: Re: apache13-php4 In-Reply-To: <38F38FEF.FD0D28DA@algroup.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 11 Apr 2000, Ben Laurie wrote: > Hmm. And what about the one where Apache-SSL replaces both > apache13-modssl and apache13-ssl? Why do you consider Apache-SSL to > need an exception, but not mod_ssl? I trust you are aware that both > need Apache to be patched before they work? The difference being that we can always patch the Apache13 port so that it will work with mod_ssl if the user decides to compile it in the future and Apache-SSL doesn't work as an APXS DSO module AFAIK. Right? -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message