in Mk/bsd.ports.mk due to ordering in Mk/bsd.port.mk. This causes OPTIONSFILE
to be incorrectly set during some make phases as a result of the recent
PKGNAMEPREFIX for apache ports.
'Revert' some of the PKGNAMEPREFIX changes for apXX-.
- Must be manually requested in tbe port Makefile either by
a) AP_FAST_BUILD=yes
b) PKGNAMEPREFIX=${APACHE_PKGNAMEPREFIX}
- Going forward, we will only do this for ports where WITH_APACHE
is NOT optional, but required. mod_* ports are a good fit.
141 ports are mod_ ports
80 of those use AP_FAST_BUILD and thus are auto hooked by this patch [a].
61 remaining are then patched to mirror the other $lang frameworks [b].
PR: ports/146956
Reported by: Hans F. Nordhaug <Hans.F.Nordhaug@hiMolde.no>, several
Discussed with: pav, itectu on #bsdports
Tested by: P6 TB run
Approved by: portmgr (pav)
Implement PKGNAMEPREFIX=ap13|ap20|ap22
*****************************************************************************
- Create packages for USE_APACHE=x ports with PKGNAMEPREFIX [1]
- Rephrase IGNORE statement, kill EOL spaces, reformat in Mk/bsd.apache.mk [2]
- Remove USE_APACHE=yes, USE_APACHE=apr, and APR_DEPS=foo
- Remove APACHE_COMPAT=X
- Drop support for 21 [dev only release, not in tree for years now]
PR: ports/115461 [1], ports/133197 [2], ports/141688
Submitted by: myself (pgollucci@),
Alexey Rubtsov <arubtsov@swsoft.com> [1],
dafne [2]
Requested by: Several [1]
Tested by: 2 -exp runs by pav
Approved by: portmgr (pav)
With Hat: apache@
This should have been part of the following previous commit to www/apache22
>- OPTIONS+= PROXY_SCGI
>
>PR: ports/140137
>Submitted by: olli hauer <ohauer@gmx.de>
We still perform a double inclusion for modules to ensure backward
compatibility
- add "Apache servers"-wide support for OPTIONS.
!! Warning !!
If OPTIONS is defined, all other modes to select modules are disabled.
Here's the logic behind:
1) OPTIONS
2) WITH_MODULES
3) all others knobs.
OPTIONS'ified list of modules can be obtained via:
"make make-options-list"
apxs does not remove module line from httpd.conf, it merely comments it out.
Later, on Apache deinstall, the file differs from stock httpd.conf and is not
deleted.
Tested by: pointyhat exprun
