xz.git - XZ Utils

Age	Commit message (Collapse)	Author	Files	Lines
2018-04-29	Bump the version number to 5.3.1alpha.larhzu/v5.3.1alpha	Lasse Collin	1	-1/+1

2017-04-24	liblzma: Add lzma_file_info_decoder().	Lasse Collin	1	-1/+6

2014-12-21	Bump version and soname for 5.2.0.	Lasse Collin	1	-1/+1
	I know that soname != app version, but I skip AGE=1 in -version-info to make the soname match the liblzma version anyway. It doesn't hurt anything as long as it doesn't conflict with library versioning rules.
2014-09-14	Bump the version number to 5.1.4beta.larhzu/v5.1.4beta	Lasse Collin	1	-1/+1

2014-06-18	liblzma: Add lzma_cputhreads().	Lasse Collin	1	-0/+1

2013-10-26	Bump the version number to 5.1.3alpha.larhzu/v5.1.3alpha	Lasse Collin	1	-1/+1

2013-03-23	liblzma: Add lzma_block_uncomp_encode().	Lasse Collin	1	-0/+1
	This also adds a new internal function lzma_block_buffer_bound64() which is similar to lzma_block_buffer_bound() but uses uint64_t instead of size_t.
2012-12-14	Make the progress indicator smooth in threaded mode.	Lasse Collin	1	-0/+1
	This adds lzma_get_progress() to liblzma and takes advantage of it in xz. lzma_get_progress() collects progress information from the thread-specific structures so that fairly accurate progress information is available to applications. Adding a new function seemed to be a better way than making the information directly available in lzma_stream (like total_in and total_out are) because collecting the information requires locking mutexes. It's waste of time to do it more often than the up to date information is actually needed by an application.
2012-07-04	Bump the version number to 5.1.2alpha.larhzu/v5.1.2alpha	Lasse Collin	1	-1/+1

2011-05-28	liblzma: Use symbol versioning.	Lasse Collin	1	-0/+105
	Symbol versioning is enabled by default on GNU/Linux, other GNU-based systems, and FreeBSD. I'm not sure how stable this is, so it may need backward-incompatible changes before the next release. The idea is that alpha and beta symbols are considered unstable and require recompiling the applications that use those symbols. Once a symbol is stable, it may get extended with new features in ways that don't break compatibility with older ABI & API. The mydist target runs validate_map.sh which should catch some probable problems in liblzma.map. Otherwise I would forget to update the map file for new releases.