Date: Wed, 15 Mar 2000 09:44:36 -0800 From: Jon Rust <jpr@vcnet.com> To: "Scot W. Hetzel" <hetzels@westbend.net> Cc: <ports@FreeBSD.ORG> Subject: Re: Why no apache-fp-ssl-php? Message-ID: <p043101beb4f57af6c8e3@[209.239.239.22]> In-Reply-To: <01f001bf8e3c$f80ac2e0$8dfee0d1@westbend.net> References: <p043101b6b4f48431bf82@[209.239.239.22]> <01f001bf8e3c$f80ac2e0$8dfee0d1@westbend.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 11:11 PM -0600 3/14/00, Scot W. Hetzel wrote: >Because creating all these apache13-a-b-c-..-x-y-z ports creates bloat in >the ports collection and makes it harder to maintain the individual >apache13-* ports (Besides the same changes needs to be made to each port >when upgrading). > >Also, having all these Apache13-* ports confuses our users, because they >have to decide if they are going to install the Apache13 port or one of the >Apache13-* ports. And then when they want to upgrade their server to use >mod_ssl, mod_frontpage, mod_x, mod_z they get discouraged because we only >support a couple of modules in each of our Apache13-* ports. Having >individual Apache Module ports allows them to add functionality to their >server as they need it. I can see your point, but in the current state of affairs, creating (for example) a working apache-fp-php-ssl build is EXTREMELY tough for non-programmers (and I'd argue tough even for adept programmers). So having many options may be confusing, but it's a lot better than not having the option at all. Right now, I need apache-fp-php-ssl. With the current port tree, I've got almost no chance of making it happen give I'm no C programmer (though I'm considering hiring one just to maintain apache builds). >Another concern is with port maintainers that do create Apache module ports, >they have to decide on which apache13-* port to support, since no two >apache13-* port installs their files in the same location and with the same >names ( httpd/apache for the server daemon, httpd.conf/apache.conf config >files, different locations for the DocumentRoot, proxy cache directory, >etc...). That sounds great. >Mathew Dodd and myself have created a Modular Apache. I just got done >tweaking it to work with FrontPage. > >It is available from: > >http://www.westbend.net/~hetzels/mod_apache.tgz Not Found The requested URL /~hetzels/mod_apache.tgz was not found on this server. Apache/1.3.9 Server at www.westbend.net Port 80 :-( No go. >There are currently, 4 ports; > > Apache13 > mod_ssl > mod_frontpage > mod_php4 > >Try them out, and let me know if they work for you. > >NOTE: Just untar them to a separate directory as they don't require being >placed under the ports collection in order to find their dependencies on the >Apache13 port. I'll give it a shot. It sounds very promising. Thanks for your reply. jon 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?p043101beb4f57af6c8e3>