Hi,

> "William A. Rowe, Jr." <[EMAIL PROTECTED]> writes:

> First, I'm pretty happy with what is going on in 2.0 HEAD now.  I
> don't think MMN is changed gratuitously, I don't think the code gets
> destabilized a whole lot on a regular basis, I think that having some
> aspects of the config change (i.e., the auth issue) change at this
> point in the >=2.0 lifetime is not completely unreasonable (scripts
> can certainly help admins).  I think we're still at a point where
> changing MMN is reasonable under certain conditions.
changing the MMN isnt the worse thing, but doing so without any documentation is!
What I expect is a list that shows for every MMN change a short description why it was 
changed or better what has changed in the sources, and if it affects third-party 
modules and which, f.e. something like that:

20020903 : added new parameter SEND_OPT in function xyz(), NULL could be passed in; 
affects filter modules.

if something like that already exists please point me to it...

Another problem why Apache2 isnt widely accepted yet (which is closely related to the 
MMN bumps):
with every new release the users have the problem that they dont find the most-wanted 
modules which then run with the new release: mod_ssl, mod_perl, mod_jk, PHP.
I bet that if the ASF would offer complete binary packages which include these modules 
then the acceptance of Apache2 would be at once much greater...

Remeber that these problems never were present with Apache 1.3.x: a PHP or mod_perl 
copmpiled for 1.3.20 still loads fine in Apache 1.3.27...; so it was never a problem 
updating Apache 1.3 to latest version except with mod_ssl...

also I think you developers around here still do not see the differences between 1.3 
and 2.0 modules:
I can still fetch an old module written for Apache 1.2, add the include of ap_compat.h 
and most Modules compile and work then without further modification; but no module 
written for 2.0.28 compiles without changes with 2.0.43 source tree...

so my experience:
compiling an old 1.3 module from 1995 is done in a few minutes;
copmpiling a module written for 2.0.2x or less from this year: dont know how long it 
lasts...

Guenter.



 

Reply via email to