Date: Tue, 20 Sep 2005 03:01:32 +0200 From: Clement Laforet <clement@FreeBSD.org> To: Doug Barton <dougb@FreeBSD.org> Cc: freebsd-ports@FreeBSD.org Subject: Re: APACHE_COMPAT and USE_APACHE? Message-ID: <20050920010132.GE40896@goofy.cultdeadsheep.org> In-Reply-To: <432F4458.9090205@FreeBSD.org> References: <432F4458.9090205@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--9l24NVCWtSuIVIod
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Sep 19, 2005 at 04:06:00PM -0700, Doug Barton wrote:
Hi Doug,
> First, while I fully appreciate the need to occasionally commit something=
=20
> without first checking with the maintainer of the port, I would appreciat=
e=20
> (as has been discussed on this list many times in the past) at least bein=
g=20
> notified of the need, and ideally pointed to some explanation of it. I=20
> _think_ I understand your commit message, but it would be nice if you cou=
ld=20
> provide some more information on this list.
>
> Also, since my port makes use of the APACHE_PORT variable, and I have=20
> noticed some commits go by that reference that in conjunction with what i=
s=20
> apparently a new variable called USE_APACHE, I would appreciate it if=20
> someone knowledgeable about these topics could describe this new stuff.
The selected patchset for next b.p.m release contains bsd.apache.mk,=20
which includes an enhanced USE_APACHE knob based on WANT_APACHE from=20
www/apache2/Makefile.modules.3rd. It supports multiple versionning=20
(e.g USE_APACHE=3D1.3+, USE_APACHE=3D2.0-, etc.), macros for apache=20
servers ((WITH|WITHOUT)_${CATEGORY}_MODULES, support for suexec,etc.),=20
some "port'n'play" macros to do quickly modules ports, and also=20
version detection based on ${APACHE_PORT}.
See www/apache2* ports and some apache modules for more detail.
It was supposed to be fully backward compatible. Kris reported me that=20
INDEX was broken. It was partially due to (ab)use of APACHE_PORT. I=20
had 2 solutions:
1. Fix all ports to be compliant with current USE_APACHE and surely=20
break maintainers logic
2. Introduce a new single variable, called APACHE_COMPAT, to restore
only APACHE_PORT support.
I enlarged my pointy hats collection with those changes, but I pretty=20
sure I made the good decision.
regards,
clem
--9l24NVCWtSuIVIod
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQFDL19ssRhfjwcjuh0RAmxSAJ4qK1mOgRWzCg/uA0Kn73TP7m5YdgCdEgV2
rZ6UoXDr4Hp62P4Gf1aUhCk=
=2FCp
-----END PGP SIGNATURE-----
--9l24NVCWtSuIVIod--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050920010132.GE40896>