ports/161758: mod_rpaf2 slave seperation and Apache22+ limitation

[Kris Persson]

>Number:         161758
>Category:       ports
>Synopsis:       mod_rpaf2 slave seperation and Apache22+ limitation
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 18 00:10:07 UTC 2011
>Closed-Date:
>Last-Modified:
>Originator:     Kris Persson
>Release:        7.2-RELEASE-p3
>Organization:
Clarke Broadcasting Corp
>Environment:
FreeBSD be1.knxs.net 7.2-RELEASE-p3 FreeBSD 7.2-RELEASE-p3 #0: Fri Sep 25 04:11:58 PDT 2009     tech at be1.knxs.net:/usr/obj/usr/src/sys/GENERIC  amd64
>Description:
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
>How-To-Repeat:
Both mod_rpaf and mod_rpaf2 are slated for deprecation on 11-1-2011.
>Fix:
I contacted maintainer apache at freebsd.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+.



>Release-Note:
>Audit-Trail:
>Unformatted: