From owner-freebsd-ports Tue Feb 6 7:27:27 2001 Delivered-To: freebsd-ports@freebsd.org Received: from yertle.kciLink.com (yertle.kciLink.com [208.184.13.195]) by hub.freebsd.org (Postfix) with ESMTP id A204037B401 for ; Tue, 6 Feb 2001 07:27:10 -0800 (PST) Received: from onceler.kciLink.com (onceler.kciLink.com [208.184.13.196]) by yertle.kciLink.com (Postfix) with ESMTP id 932492E440 for ; Tue, 6 Feb 2001 10:27:07 -0500 (EST) Received: (from khera@localhost) by onceler.kciLink.com (8.11.1/8.11.1) id f16FR7874726; Tue, 6 Feb 2001 10:27:07 -0500 (EST) (envelope-from khera) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14976.6091.425890.658134@onceler.kciLink.com> Date: Tue, 6 Feb 2001 10:27:07 -0500 To: ports@freebsd.org Subject: Re: Apache mod_ ports In-Reply-To: <20010205180431.D17025@mail.vcnet.com> References: <20010205180431.D17025@mail.vcnet.com> X-Mailer: VM 6.90 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> "JR" == Jon Rust writes: JR> Are port maintainers making progress here? I notice that Frontpage and JR> SSL are still absent from the list of mod_* ports. Any hope of getting JR> either of them? I'm still using Scot Hetzel's first attempt[1] at this, JR> and feel myself falling a bit behind, apache-wise. The thing with mod_ssl is that it requires extensions to the Apache API. I don't see how you can do that with a stand alone package that is installed after Apache is built. Please explain how you expect this to work. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-240-453-8497 AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message