search

Docker-J / lz4

Automatically exported from code.google.com/p/lz4
0 stars 0 forks source link

lz4io license #143

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Although I can understand lz4cli license needs to be GPL due to getopt(), why 
lz4io is also licensed under GPL?
It seems LZ4F API is going to be added, but I sometimes want to refer to lz4io.

Note: I have written yet another lz4c handler without using lz4io: 
http://pastebin.com/yqt1avdt

Original issue reported on code.google.com by cielarti...@gmail.com on 6 Oct 2014 at 11:39

GoogleCodeExporter commented 9 years ago 
The plan is indeed to have LZ4F API (already BSD license) as part of lz4 
library.

Then lz4io will be modified to make use of LZ4F, instead of using its own 
internal routines.

Then it will be time to consider the proper license for lz4io.

Original comment by yann.col...@gmail.com on 6 Oct 2014 at 11:42

GoogleCodeExporter commented 9 years ago 
Somewhat related :
a new version of lz4io has been released (currently in beta mode).
It strips most of its logic, now handled by lz4frame.

The new version can be accessed at :
https://github.com/Cyan4973/lz4/tree/dev

Original comment by yann.col...@gmail.com on 30 Nov 2014 at 5:10

GoogleCodeExporter commented 9 years ago 
The supported migration path is to use lz4frame library

Original comment by yann.col...@gmail.com on 31 Mar 2015 at 1:38

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
What I mean is: Do you have any plan to update lz4cli to use lz4frame?

Original comment by cielarti...@gmail.com on 31 Mar 2015 at 2:54

GoogleCodeExporter commented 9 years ago 
Well, it already does.

lz4cli uses lz4io which uses lz4frame.
There is no more logic inside lz4io, everything is delegated to lz4frame.

Original comment by yann.col...@gmail.com on 31 Mar 2015 at 2:54