Closed GoogleCodeExporter closed 8 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
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
The supported migration path is to use lz4frame library
Original comment by yann.col...@gmail.com
on 31 Mar 2015 at 1:38
[deleted comment]
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
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
Original issue reported on code.google.com by
cielarti...@gmail.com
on 6 Oct 2014 at 11:39