Date: Fri, 1 Oct 1999 01:24:38 -0500 From: "Bill McMilleon" <billm@flink.com> To: <freebsd-questions@FreeBSD.ORG> Subject: ports versus manual installs? Message-ID: <000201bf0bd5$a3daac60$6401a8c0@mchome> In-Reply-To: <Pine.BSF.4.10.9910010030290.19213-100000@kg.ops.uunet.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello. I'd like to thank those of you out there in this group who are helping support us FreeBSD neopythes in our quest for knowledge. After playing with 3.2R and 3.3R over the past several weeks I can see that its a breeze to install just about any port and that its a very convenient way to "try something out." But when it comes installation of a specific or unusual configuration for which no port is provided, is it always necessary to totally do things manually from start to finish, ignoring the ports collection altogether? For example, there are several apache 1.3.9 ports in different "flavors" (with php3.0.12, with ssl, etc), but what if I need apache1.3.9+php3.0.12+PyApache or httpdapy -- must I compile the whole thing manually, or can I use the port to get started with apache139+php3 then EASILY add the other, more unusual parts later? I'm finding apache to be one of the biggest challenges to install -- seems like all that flexibility comes at quite a cost up front in the form of a steep learning curve! Releated to to this also: why when I install apache the ports collection do I get a binary named apache instead of httpd and everything is in a different location than it would be had I manually compiled the app using directions from www.apache.org? Bouncing back and forth between ports and manual processes becomes very confusing to a newbie when all the file locations and even some of the file names change. TIA, Bill McMilleon Alltel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000201bf0bd5$a3daac60$6401a8c0>