Before submiting this PR I have checked to make sure a PR of this nature had not already been submitted. I also reviewed current ports/UPDATING and src/UPDATING to be sure.
mod_rpaf and mod_rpaf2 are master slave ports. I use mod_rpaf2 on apache22 with nginx front end. mod_rpaf2 is useable with apache22+.
apache-2.2.20_1 Version 2.2.x of Apache web server with prefork MPM.
ap22-mod_rpaf-0.6_1 Make proxied requests appear with client IP
nginx-0.8.54 Robust and small WWW server
I contacted maintainer firstname.lastname@example.org and per Phillip M. Gollucci of Apache he suggested the following:
"What should happen is mod_rpaf becomes mod_rpaf2 with the appropriate changes to make it only for 22+, then mod_rpaf can quietly go away when apache13/20 do."
This will require a change to the ports themselves as they are currently linked as master/slave though the slave works with apache22+.
How-To-Repeat: Both mod_rpaf and mod_rpaf2 are slated for deprecation on 11-1-2011.
Over to maintainer (via the GNATS Auto Assign Tool)
ohauer 2012-01-01 17:37:17 UTC
FreeBSD ports repository
www/mod_rpaf2 distinfo pkg-descr
- rewrite mod_rpaf2 so it is not a subport of mod_rpaf
(prepare to remove www/apache13 and depending www/mod_rpaf)
with hat apache@
Submitted by: Kris Persson <email@example.com>
Revision Changes Path
1.7 +16 -3 ports/www/mod_rpaf2/Makefile
1.1 +2 -0 ports/www/mod_rpaf2/distinfo (new)
1.1 +8 -0 ports/www/mod_rpaf2/pkg-descr (new)
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "email@example.com"
Thanks for the hint!
mod_rpaf2 builds now on it's own