From owner-freebsd-ports Sun Apr 27 11:40:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA22742 for ports-outgoing; Sun, 27 Apr 1997 11:40:58 -0700 (PDT) Received: from nexis.net (customer-1.ican.net [198.133.36.101]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA22728; Sun, 27 Apr 1997 11:40:48 -0700 (PDT) Received: from localhost (james@localhost) by nexis.net (8.8.5/8.8.5) with SMTP id OAA19282; Sun, 27 Apr 1997 14:40:12 -0400 (EDT) Date: Sun, 27 Apr 1997 14:40:12 -0400 (EDT) From: James FitzGibbon To: Chuck Robey cc: freebsd-ports@freebsd.org, ache@freebsd.org Subject: Re: Suggested change to apache port In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 27 Apr 1997, Chuck Robey wrote: > directory to exist using the BUILD_DEPENDS stuff, which would get the > fetch/patch/whatever done for you. That part at least is simpler now > that that used in those old tcl/tk things, which used to do cd's and > makes (I found that real ugly!) But wouldn't build depends go into ${PORTSDIR}/www/apache and do a make install ? If someone had made modifications to their webserver and then made mod_perl, they'd end up with an httpd binary containing just mod_perl and not their previous configured modules. Do we have to admit that the existing ports system doesn't lend itself to people who stray from the baseline ports ? -- j.