From owner-freebsd-ports Sun Apr 27 11:37:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA22635 for ports-outgoing; Sun, 27 Apr 1997 11:37:02 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA22630; Sun, 27 Apr 1997 11:36:56 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/8.7.3) with SMTP id OAA06204; Sun, 27 Apr 1997 14:36:54 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id OAA10183; Sun, 27 Apr 1997 14:36:51 -0400 Date: Sun, 27 Apr 1997 14:36:16 -0400 (EDT) From: Chuck Robey To: James FitzGibbon 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, James FitzGibbon wrote: > I've received a request to port the perl5 Apache module (integrates perl > into the server for CGI's and modules). It would be a pretty easy task, > but in order to build mod_perl.o, I need to Apache source files. > > The existing apache port doesn't install the source files anywhere. I > realize that this is against the standard for ports, but I think that in > the case of Apache, we have a valid case for doing so. Some of the old tcl/tk stuff used to do this. I think they handled it by doing a make configure on the other sources they needed, then copying as required. This has the drawback of requiring an absolute location of the apache port (it would have to be in $(PORTSDIR)/www/apache), but I think this cost is less than the alternative, which requires everyone to store the sources. That sounds more aberrant, to me. You could just force the 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!) At least this would do away with the need (you brought up) to store the sources for apache separately, or to otherwise gen up a new, separate source dist which you'd have to keep current. Anyhow, that's my suggestion. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+-----------------------------------------------