Philip M. Gollucci pgollucci at
Mon Apr 13 13:29:57 PDT 2009

Pav Lucistnik wrote:
> Infrastructure changes does not go to UPDATING, they are of no interest
> to end users. The file you want to put these into is CHANGES.
Ack. Figured.

> The text you wrote for CHANGES is a mission statement and does not
> belong anywhere. Drop it.
I'll come up with something simpler, and smaller.

> Is there a problem with supporting both? I think it's kinda nice.
No, but I like uniformity.  It can stay.

>> Next up, I'd like to make which is for www/mod_perl*
>> and will let me remove the WITH_APACHE and WITH_APACHE2 from ports
>> that can use either. (USE_MP=13|20 and USE_APREQ=13|20)
> Why new include file, cannot it be folded into ?
Sure it could be, but I wanted to do it distinctly as large amounts of need twiki/updating/modernizing.  Why the general thoughts of no
new files in Mk/ ?  Is there an overhead I'm missing ?

It might even be worth it to start distinctly and later pull it back in.

>> Then, with I think should start with just support for
>> www/apache*.  zope, ngix, lighttpd, etc.. should be added next 1 at a time.
> This sounds like an overkill, but I haven't seen the details.
Not really. Its also largely requested by committers, users, and other.

The end result being something like:

USE_WEBSERVER=	apache20+ ngixX+ zopeY- lighttpdZ

Somewhere you set WEB_SERVER=foo (sort of like APACHE_PORT)

Then using and additions it kind of just works.

Its kind of analogous to the Widget Factory pattern or maybe Sigleton.

1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70  3F8C 75B8 8FFB DB9B 8C1C
Philip M. Gollucci (pgollucci at c: 703.336.9354
Consultant          - P6M7G8 Inc.      
Senior Sys Admin    - RideCharge, Inc. 
Contractor          - PositiveEnergyUSA
ASF Member          - Apache Software Foundation
FreeBSD Committer   - FreeBSD Foundation

Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.

More information about the freebsd-apache mailing list