Date: Sat, 1 May 1999 11:21:02 -0500 From: "Scot W. Hetzel" <hetzels@westbend.net> To: "Neil Blakey-Milner" <nbm@mithrandr.moria.org> Cc: <ports@FreeBSD.ORG> Subject: Re: Dialog-based configuration tool for ports Message-ID: <007a01be93ee$9b6a7f60$8dfee0d1@westbend.net> References: <19990501154746.A70833@rucus.ru.ac.za>
next in thread | previous in thread | raw e-mail | index | archive | help
From: Neil Blakey-Milner <nbm@mithrandr.moria.org> > At the moment, I have one major problem. My reason in creating this > tool was hopefully to break down the apache13-fp-php3-ssl-mod_perl and > apache13-fp-ssl-mod-perl and apache13-php3-ssl sort of mentality (which > apache13-php3 does reasonably well, and which I used as the inspiration > for this program). > The Ideal solution for the apache13-* problem is to create individual ports for each apache module. We create one Apache13-mod port that is compiled with all required patches (mod_ssl EAPI patch, mod_frontpage misclaneous patches, other module patches) it needs to be compatible with the module ports. Then we create the following module ports with a dependency on the Apache13-mod port. mod_frontpage mod_ssl mod_PHP3 mod_perl mod_etc.... This helps the Web Administrator out, because he will not have to compile a Apache13-* port that has all of the modules compiled into it. Instead he can add/remove modules as his requirements for a web server changes without the need to recompile the entire web server. Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?007a01be93ee$9b6a7f60$8dfee0d1>