[MacPorts] #20516: apache2, apache20: mpm variant issues

[MacPorts]

#20516: apache2, apache20: mpm variant issues
-------------------------------------+--------------------------------------
 Reporter:  ryandesign@…             |       Owner:  imajes@…           
     Type:  defect                   |      Status:  new                
 Priority:  Normal                   |   Milestone:                     
Component:  ports                    |     Version:  1.7.1              
 Keywords:                           |        Port:  apache2, apache20  
-------------------------------------+--------------------------------------
 I've never looked into the mpm variants in apache2 (and apache20) before,
 but now that I do, I see a number of issues.

  1. The three mpm variants are mutually exclusive so they should be marked
 as conflicting with one another
  2. They should have variant descriptions
  3. One of them should be marked as a default variant if no other mpm has
 already been chosen:
   1. Either the preforkmpm variant should be default, since the comment in
 the portfile reads "This ends up being the default mpm if no other is
 chosen"
   2. Or the workermpm variant should be default, since the comment for
 that variant reads "This mpm is probably preferred (maybe we should make
 it a default variant?)"

 It may be wise to do 3.1 now and increase the revision, then wait a few
 months to ensure most users have upgraded to that version, and only then,
 if 3.2 is the actual desired end result, do 3.2 then. That way, existing
 users who already have the preforkmpm will not suddenly be switched to the
 workermpm, which might have adverse effects (e.g. don't you have to
 recompile php and all your php modules if you change apache mpms?)

-- 
Ticket URL: <http://trac.macports.org/ticket/20516>
MacPorts <http://www.macports.org/>
Ports system for Mac OS