X-Git-Url: https://wimlib.net/git/?p=wimlib;a=blobdiff_plain;f=NEWS;h=74052dc345e7e024784c68f31f08604b652ff773;hp=1fba3b55580bb72ae5416250737846b4ddd6bb98;hb=93ff837938b51373bc60153ef60409f6c1f795c8;hpb=343b098498118f1554bd476d00d8233ec0cb9a6b diff --git a/NEWS b/NEWS index 1fba3b55..74052dc3 100644 --- a/NEWS +++ b/NEWS @@ -1,40 +1,171 @@ -Only the most important changes more recent than version 0.6 are noted here. +Version 1.7.1-BETA: + The new (as of v1.7.0) extraction code will no longer run out of file + handles when extracting many (1000+) identical files. + + Library users can now initialize and de-initialize the library multiple + times in one run of an application program. + + Library users will now receive WIMLIB_PROGRESS_MSG_WRITE_STREAMS and + WIMLIB_PROGRESS_MSG_EXTRACT_STREAMS messages more frequently when + writing or extracting large WIM files. + + Added experimental new write flag: + WIMLIB_WRITE_FLAG_SEND_DONE_WITH_FILE_MESSAGES. + +Version 1.7.0: + Improved compression, decompression, and extraction performance. + + Improved compatibility with version 3584 WIM / ESD files: + - Add support for reading and writing multiple solid blocks per + archive, which WIMGAPI/DISM can create when appending an image. + - Correctly create solid blocks larger than 4 GiB. + + 'add' commands passed to wimupdate will now replace existing + nondirectory files by default. Use the --no-replace option to get the + old behavior. + + The license for the library now contains an exception that allows using + it under the LGPL. See the COPYING file for details. + + In reparse-point fixup mode (the default for capture), symbolic links + and junctions that point outside the tree being captured are no longer + excluded from capture. + + Added support for "WIMBoot" capture and extraction. See the + documentation for the new '--wimboot' option to wimcapture and wimapply + for more information. + + On UNIX-like systems, you can now backup and restore device nodes, named + pipes, and sockets. In addition, 32-bit user and group IDs are now + supported. + + The way that UNIX data is stored in WIM files has been changed. If you + captured any WIMs with the --unix-data option, to upgrade them you'll + need to apply them with --unix-data using wimlib-imagex v1.6.2, then + re-capture them with --unix-data using this version. + + wimlib now understands tagged metadata items, such as object IDs, that + can be stored in WIM directory entries. + + Removed the --hardlink and --symlink options to wimapply, since I don't + think they are too useful and they got in the way of improving the code. + + WIMs will now retain their GUIDs when rebuilt (e.g. with wimoptimize). + + The 'mkwinpeimg' script now supports writing the ISO image to standard + output. + + The element in WIM XML data is now exported correctly. + + On Windows, sparse file attributes are no longer set on extracted files. + Oddly enough, this actually saves disk space in some cases. + + On UNIX, configuring with --disable-xattr or --enable-xattr is no longer + supported. Mounting WIM images now always requires extended attribute + support. Use --without-fuse to disable support for mounting WIM images; + this will also disable the need for extended attribute support. + + Configuring with --enable-ssse3-sha1 now works correctly. + + The shared library version has been bumped up. The main + incompatibilities are: + + - WIMLIB_COMPRESSION_TYPE_XPRESS is now 1 and + WIMLIB_COMPRESSION_TYPE_LZX is now 2 (so it's the same as + WIMGAPI). + + - User-provided progress functions are now registered using a + separate function, wimlib_register_progress_function(). The + 'progress_func' argument to many functions no longer exists. + + - The return value from user-provided progress functions is now + significant. + + - A context argument has been added to the prototype of + user-provided progress functions. + + - 'struct wimlib_capture_config' has been removed. The library + now takes the path to the configuration file directly. This + affects wimlib_add_image(), wimlib_add_image_multisource(), + and wimlib_update_image(). However, a NULL value passed in + the argument retains the same meaning. + + - Removed deprecated functions: some (de)compression functions, + wimlib_extract_files(), and wimlib_print_metadata(). + + - Removed extraction flags: WIMLIB_EXTRACT_FLAG_HARDLINK, + WIMLIB_EXTRACT_FLAG_SYMLINK, WIMLIB_EXTRACT_FLAG_FILE_ORDER, + and WIMLIB_EXTRACT_FLAG_SEQUENTIAL. + + - Removed some progress messages: + WIMLIB_PROGRESS_MSG_APPLY_TIMESTAMPS, + WIMLIB_PROGRESS_MSG_EXTRACT_DIR_STRUCTURE_BEGIN, + WIMLIB_PROGRESS_MSG_EXTRACT_DIR_STRUCTURE_END. Numbering + stays the same. + + - Removed some error codes. Numbering stays the same. + + - Replaced WIMLIB_UNMOUNT_FLAG_LAZY with + WIMLIB_UNMOUNT_FLAG_FORCE. + + - WIM paths passed to progress functions now have a leading + slash. + +Version 1.6.2: + Case-insensitive comparisons of strings (e.g. filenames) containing + UTF-16 codepoints above 32767 are now done correctly. + + Fixed build failure on Mac OS X. + + wimunmount now provides the '--new-image' option to cause changes to a + read-write mounted image to be committed as a new image rather than as + an update of the mounted image. (The corresponding new library flag is + WIMLIB_UNMOUNT_FLAG_NEW_IMAGE.) + + The LZMS ("recovery") compression chunk size, or "dictionary size", may + now be up to 1 GiB (1,073,741,824 bytes). + + The performance of LZX ("maximum") and LZMS ("recovery") compression + with large chunk sizes has been slightly improved. Version 1.6.1: Stored files with size exactly 4 GiB (4,294,967,296 bytes) are now decompressed correctly. + Fixed a bug in the LZX compressor introduced in v1.5.3. The bug + occurred in an unlikely case, and due to validity checks it did not + affect successfully created archives. + Fixed a minor compatibility issue with the LZMS compressor and decompressor. This is *not* the default compression type and was only - introduced in v1.6.0. In the unlikely event that you created a + introduced in v1.6.0. In the unlikely event that you created an LZMS-compressed WIM with v1.6.0 and a checksum error is reported when applying it with v1.6.1, decompress it with v1.6.0 then compress it with v1.6.1. - Fixed more permissions problems when extracting files on Windows. - Memory usage for LZMS and LZX compression has been decreased. + wimextract now allows wildcard characters in paths specified on the + command line. Also, the '--strict-wildcards' option has been removed + and replaced with the inverse option '--nullglob'. See the + documentation for wimextract for more details and changes. + + The wimlib_extract_files() function is now considered deprecated in + favor of wimlib_extract_paths(). + + Fixed more permissions problems when extracting files on Windows. + A new '--no-attributes' option has been added to wimapply and wimextract. The library flag is WIMLIB_EXTRACT_FLAG_NO_ATTRIBUTES. The default chunk size is now set correctly when changing the - compression type of a WIM (this bug caused wimoptimize to fail when - changing the compression type from None to LZX with no chunk size - explicitly specified, for example). - - wiminfo no longer accepts the '--metadata' option. Use the new - '--detailed' option to wimdir instead. (This is primarily for - debugging.) - - Paths passed to wimlib_extract_paths() and wimlib_iterate_dir_tree() may - now use either forwards or backwards slashes, as documented. + compression type of a WIM, for example with 'wimoptimize'. - Fixed a potential stack overflow when extracting solid archives - containing more than about 100000 files. + The '--metadata' option to wiminfo has been replaced with the + '--detailed' option to wimdir. - For wimcapture, wimoptimize, and wimexport, '--solid' may now be used as - an alias for '--pack-streams'. + In relevant wimlib-imagex commands, '--solid' may now be used as an + alias for '--pack-streams'. Version 1.6.0: Support for extracting and updating the new version 3584 WIMs has been