In a message dated 01-09-04 09:35:50 EDT, Jim wrote...
> >That's right.... and one of them is...
> >
> >Will Apache accept ZLIB into the Apache source tree in either
> >source or binary library format for all platforms.
> >
> >Check one box only...
> >
> >[__] Yes
> >[__] No
> >
>
> Actually, it's not a binary answer... Since Yes implies that the
> ASF would accept binary library, which ain't the case, and No implies
> that we wouldn't accept source, which may not be....
Yea... I guess the minute I hit send I realized that 'if' statement
was missing some 'else'. ROFL
How about this...
Will the Apache group accept the ZLIB source code
into the distribution tree at this time?...
[__] Yes
[__] No
if ( Yes )
{
1. Where will it be? /srclib/zlib?
2. Who is going to add it and when?
}
else
{
Will Apache accept pre-compiled ZLIB libraries into the
source tree ( for any/all platforms )?
[__] Yes
[__] No
if ( Yes )
{
1. Where will the ZLIB libraries be? /srclib/? /support/zlib?
2. Who is going to add them and when?
}
else
{
1. How can anyone vote on adding Ian's mod_gz to the source tree
when the public domain libraries it needs can't be in the source
tree?
2. How is anything in Apache that ever needs ZLIB supposed to
compile? Users must always 'go and get' the libs themselves?
}
}/* End 'else' */
> zlib is a very large chunk of code,
Not really... but I guess some might think so.
ASIDE: You really only need the 'compression' part of it. You
are a Server, not a client.
> and we resist requiring external
> code unless:
>
> 1. It's small
> 2. It's very stable (ie: don't have to keep updating it all the
> time, nor worry about passing patches back).
> 3. It's used by a large chunk of the Apache code (eg: regex).
> Does zlib fit the bill?? Well, not for #1 and not really for #3...
Numbers 1 and 2 already sound like the compressor that's
in mod_gzip and is NOT ZLIB ( minus all the debug code, of course ).
It's VERY stable and VERY small ( 20k or so ).
As for number 3... I am still of the opinion that your perspective
is wrong... you are playing 'chicken or egg'. I am of the opinion
that if ZLIB WAS there then in very short order there WOULD
be a 'large chunk of Apache code' that uses it. This is ( and I guess
always has been ) my point.
'Build it and they will come...'
'Include the libs and they will be used ( a lot )...'
Something like that
How in the heck tod the REGEX stuff ever make it in?
Was that some huge 'catch 22' or 'chicken and egg' scenario
as well when it was being proposed?
What was the final straw that broke the stalemate over the
'regexec' library inclusion(s)?
> Does that mean we'd never consider it... I'm not willing to say so.
Then it's happening all over again.
Everyone has an opinion but no one will VOTE one
way or the other.
What's it going to take to find out once and for all if
ZLIB can be included in the Apache source tree?
I don't know anymore. I've tried to explain why I think
it would be a great benefit to Apache to have it there
( numerous times going back over a year or more )
and I have tried to supply as much information as I
have about the licensing issues ( IANAL ) and I
have asked for 'real' votes about it... nothing happens...
just more talk.
Somebody else needs to take this into the end-zone.
I don't even know where the football is on this one
anymore.
Yours...
Kevin Kiley
