| Commit History - (may be incomplete: see CVSWeb link above for full details) |
| Date | By | Description |
20 Aug 2011 17:27:52
  1.15_1
|
ohauer  |
- bump PORTREVISION from ports if USE_APACHE=13+ or 20+ is defined |
19 Mar 2011 12:38:54
1.15
|
miwi |
- Get Rid MD5 support |
07 Jun 2010 04:39:23
1.15
|
pgollucci |
- Convert to AP_FAST_BUILD / AP_GENPLIST
- swap LOCAL site for mine
- Pet Portlint |
27 May 2010 21:27:03
1.15
|
pgollucci |
- 2/3:
- consistently use APACHE PLIST_SUB var %%AP_NAME%% in pkg-plists
PR: ports/147142
Reviewed by: portmgr (pav)
With Hat: apache@ |
25 May 2010 20:17:37
1.15
 |
pgollucci |
Mk/bsd.apache.mk can not sufficiently alter things before Mk/bsd.options.mk
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) |
28 Aug 2009 17:37:26
1.15
|
linimon |
Reset chinsan@FreeBSD.org due to numerous maintainer-timeouts and no
response to email.
Hat: portmgr |
21 May 2009 20:45:34
1.15
|
pgollucci |
- Mark remaining mod_* ports MAKE_JOBS_SAFE=yes
PR: ports/134611
Approved by: pav (#bsdports) |
28 May 2008 12:36:05
1.15
|
chinsan |
Add mod_fileiri, a http IRIs module for Apache 2.
mod_fileiri implements http IRIs for directories/files, i.e.
if accepts URIs with non-ASCII characters encoded in UTF-8 and
converts them to the legacy encoding used in the file system
(which can be specified per directory, or even finer if necessary
(although that's a real hack)).
What is more, it continues to accept requests in the legacy
encoding specified, and redirects them to the correct UTF-8
form, which then returns the actual document (without looping).
There is also a backwards mode, which does redirects from
URIs in a specified legacy encoding to UTF-8 if the directory/
filenames are in UTF-8.
WWW: http://www.w3.org/2003/06/mod_fileiri/ |
