From owner-freebsd-apache@FreeBSD.ORG Fri Dec 17 14:56:06 2004 Return-Path: Delivered-To: freebsd-apache@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F5CA16A4CE; Fri, 17 Dec 2004 14:56:06 +0000 (GMT) Received: from miffy.openlook.org (openlook.org [211.236.182.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 766E743D53; Fri, 17 Dec 2004 14:56:05 +0000 (GMT) (envelope-from perky@miffy.openlook.org) Received: by miffy.openlook.org (Postfix, from userid 1000) id 1F885A927; Fri, 17 Dec 2004 23:56:04 +0900 (KST) Date: Fri, 17 Dec 2004 23:56:04 +0900 From: Hye-Shik Chang To: Clement Laforet Message-ID: <20041217145603.GA5890@i18n.org> References: <20041217111953.7a685375.clement@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="azLHFNyN32YCQGCU" Content-Disposition: inline In-Reply-To: <20041217111953.7a685375.clement@FreeBSD.org> X-Accept-Language: ko, en User-Agent: Mutt/1.5.6i cc: apache@FreeBSD.org cc: perky@FreeBSD.org Subject: Re: [proposal] modular envvars X-BeenThere: freebsd-apache@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Support of apache-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Dec 2004 14:56:06 -0000 --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 17, 2004 at 11:19:53AM +0100, Clement Laforet wrote: > [ perky@ is Cc'd since www/mod_python3 could use it ] >=20 > Guys, >=20 > At the moment, envvars is deleted during upgrade, which is *ugly*. I > could compare envvars and envvars-std, but I'd like to make envvars > modular. For example you put your stuff in > ${PREFIX}/etc/apache/envvars/*.env and it will be automatically read by > envvars (at the _end_ of the file). >=20 > How do you like the idea? >=20 I'll be happy if we adopt debian-like config installation system here. It will be like this: apache2 port creates a directory on its installation: /usr/local/sbin/apache2-envvars.d/ And apache module ports which wants some modification on envvars (namely, www/mod_python{,3}) install its own configuration under there: /usr/local/sbin/apache2-envvars.d/mod_python.sh /usr/local/sbin/apache2-envvars.d/mod_python3.sh /usr/local/sbin/apache2-envvars.d/mod_yet_another.sh And, envvars contains a script which traverses the directory. like: for f in /usr/local/sbin/apache2/envvars.d/*; do source $f; done I found this idea from debian's apache package and it looks very useful for not only envvars but also httpd.conf. (we have several ports that needs modification on httpd.conf in the ports already) It was just an idea. :-) Hye-Shik --azLHFNyN32YCQGCU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBwvODDWUsWc/bS6QRArvVAKCRU5mLnJTe2QOgoTUSVAAdT8oyxwCfeJgQ R6hgB36555uIXDsmP/FJfvQ= =/e8s -----END PGP SIGNATURE----- --azLHFNyN32YCQGCU--