From owner-freebsd-questions  Thu Jul 24 10:12:04 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id KAA12061
          for questions-outgoing; Thu, 24 Jul 1997 10:12:04 -0700 (PDT)
Received: from ns.tar.com (ns.tar.com [204.95.187.2])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA12008
          for <freebsd-questions@freebsd.org>; Thu, 24 Jul 1997 10:11:57 -0700 (PDT)
Received: from ppro.tar.com (ppro.tar.com [204.95.187.9])
	by ns.tar.com (8.8.6/8.8.5) with SMTP id MAA04110;
	Thu, 24 Jul 1997 12:10:11 -0500 (CDT)
Message-Id: <199707241710.MAA04110@ns.tar.com>
From: "Richard Seaman, Jr." <lists@tar.com>
To: "Joshua Fielden" <shaggy@houseofduck.dyn.ml.org>,
        "Shawn Ramsey" <shawn@luke.cpl.net>
Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
Date: Thu, 24 Jul 97 12:10:09 -0500
Reply-To: "Richard Seaman, Jr." <lists@tar.com>
Priority: Normal
X-Mailer: PMMail 1.92 For OS/2
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: RE: Apache and Ports Policies in General
Sender: owner-freebsd-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Thu, 24 Jul 1997 09:22:31 -0700 (PDT), Shawn Ramsey wrote:

>> While I do have to agree in theory with you, I went to Apache.org and
>> got 1.2.1, and it compiled "out-of-the-box." It seems from the web page
>> that they make a special point of listing FreeBSD as one of the
>> platforms that it does do this on.
>
>I think the souce is as easy as the port to compile. Just type ./Configure
>; make ; make install. :)

I agree with both these statements.  In this case we should just do away
with the "port" altogether ;)

But, unless I'm mistaken, there is one complication.  If you already
have an earlier version of apache installed from the ports collection,
the FreeBSD port "patches" apache to use directories and other
configuration options that are different from the stock apache distribution.

Now, if you want to upgrade to the current version of apache as you suggest,
but using the stock apache distribution, you have to either change your
existing directory structure and accept a different configuration mix,
or go in and hand patch the file Configuration to match what you had before. 
Granted, this is not the end of the world, but it sure makes having used the
"ports" collection a lot less convenient.