From owner-freebsd-ports Tue Jan 4 21:23:45 2000 Delivered-To: freebsd-ports@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 85EEC14ED8 for ; Tue, 4 Jan 2000 21:23:42 -0800 (PST) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id AAA12928 for ; Wed, 5 Jan 2000 00:23:54 -0500 (EST) (envelope-from bsdx@looksharp.net) Date: Wed, 5 Jan 2000 00:23:54 -0500 (EST) From: Adam To: freebsd-ports@freebsd.org Subject: Re: ports/15873: New Apache_fp+php+mod_ssl-1.3.9+3.0.12+2.4.8 port. In-Reply-To: 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 That would be nice too but IMHO it would be important to have ports that can integrate their features into an existing apache install as a webserver's needs grow. my two cents On Wed, 5 Jan 2000, Bill Fumerola wrote: >On Wed, 5 Jan 2000, Patrick Bihan-Faou wrote: > >> To me the ideal situation would be: >> - a simple apache port (apache13) >> - a new port category (maybe) for the apache modules where I could find >> mod_ssl, mod_php, mod_frontpage, mod_xyz, etc. > >and the apache13 port might also have a dialog script that could choose >all of the above (and resolve conflicts etc). > >-- >- bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - >- ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - > > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-ports" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message