![]() |
![]()
| ![]() |
![]()
NAMElibarchive_changes —
changes in libarchive interface
CHANGES IN LIBARCHIVE 3This page describes user-visible changes in libarchive3, and lists public functions and other symbols changed, deprecated or removed in libarchive3, along with their replacements if any.Multiple FiltersLibarchive2 permitted a single (input or output) filter active on an archive. Libarchive3 extends this into a variable-length stack. Wherearchive_write_set_compression_XXX () would replace any
existing filter, archive_write_add_filter_XXX ()
extends the write pipeline with another filter.
Character Set HandlingLibarchive2 assumed that the local platform uses Unicode as the native wchar_t encoding, which is true on Windows, modern Linux, and a few other systems, but is certainly not universal. As a result, pax format archives were written incorrectly on some systems, since pax format requires UTF-8 and libarchive 2 incorrectly assumed that wchar_t strings can be easily converted to UTF-8.Libarchive3 uses the standard iconv library to convert between character sets and is introducing the notion of a “default character set for the archive”. To support this, archive_entry objects can now be bound to a particular archive when they are created. The automatic character set conversions performed by archive_entry objects when reading and writing filenames, usernames, and other strings will now use an appropriate default character set: If the archive_entry object is bound to an archive, it will use the default character set for that archive. The platform default character encoding (as returned by
Libarchive3 also introduces charset options to many of the archive readers and writers to control the character set that will be used for filenames written in those archives. When possible, this will be set automatically based on information in the archive itself. Combining this with the notion of a default character set for the archive should allow you to configure libarchive to read archives from other platforms and have the filenames and other information transparently converted to the character encoding suitable for your application. Prototype ChangesThese changes break binary compatibility; libarchive3 has a new shared library version to reflect these changes. The library now uses portable wide types such as int64_t instead of less-portable types such as off_t, gid_t, uid_t, and ino_t.There are a few cases where these changes will affect your source code:
Affected functions:
Where these functions or their arguments took or returned gid_t, ino_t, off_t, or uid_t they now take or return int64_t or equivalent. Deprecated SymbolsSymbols deprecated in libarchive3 will be removed in libarchive4. These symbols, along with their replacements if any, are listed below:
Removed SymbolsThese symbols, listed below along with their replacements if any, were deprecated in libarchive2, and are not part of libarchive3.
SEE ALSOarchive_read(3), archive_read_filter(3), archive_read_format(3), archive_read_set_options(3), archive_util(3), archive_write(3), archive_write_filter(3), archive_write_format(3), archive_write_set_options(3), libarchive(3)
|