httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From TOKI...@aol.com
Subject Re: [PATCH] ap_add_filter
Date Sun, 20 Aug 2000 17:37:23 GMT

In a message dated 00-08-20 16:47:40 EDT, you write:

> > deflate, inflate, GZIP and ZLIB are all still GNU only.
>  
>  bzzt.
>  
>  zlib is under an apache/bsd-like license.
>  
>  http://www.info-zip.org/pub/infozip/zlib/zlib_license.html

Ok.. that's good.

That still doesn't answer the question about will the inclusion
of ZLIB with Apache source be AOK or not but it's a start.

If someone dumped a filter into Apache code base TOMORROW
that simply had re-written ZLIB code in it is that perfectly
acceptable or would there be any issues at all to talk about?

In other words... is it a total GREEN light or is the light
still YELLOW on this one?

What about 'deflate' and 'inflate' which is what ZLIB uses?
I thought that was pure GNU stuff?
Doesn't that make ZLIB a 'derivative' work and doesn't that
mean all of ZLIB is still, technically, GNU?
Maybe I still just don't understand 'copyleft'.

I read the ZLIB license... I still don't really get it.

Obviously the people that fear 'copyleft' and the GNU stuff
are still those who don't think every piece of code they have
should be freely available for public consumption but in
Apache's case I don't understand why the whole GNU thing
is even an issue.

ALL of Apache is already open-source and public anyway so why
should there ever be a concern about dumping GNU code 
into Apache itself? You have nothing to lose. Or am I still
totally missing something about ASF license versus GNU?

Yours...
Kevin Kiley

Mime
View raw message