diff options
| author | joerg <joerg@pkgsrc.org> | 2019-09-22 09:51:28 +0000 |
|---|---|---|
| committer | joerg <joerg@pkgsrc.org> | 2019-09-22 09:51:28 +0000 |
| commit | 85efd7f8759590df15b06d680dc2c141a499d7d3 (patch) | |
| tree | 89973fc4fc77a5c0ac5daa4ea8e0e1afbf23fbf5 /archivers/libarchive/files/doc/html | |
| parent | 3d58b3c8e51f686500fbe08fc5fea947dfa036b4 (diff) | |
| download | pkgsrc-85efd7f8759590df15b06d680dc2c141a499d7d3.tar.gz | |
Import libarchive 3.4.0KIENTZLE
Diffstat (limited to 'archivers/libarchive/files/doc/html')
44 files changed, 551 insertions, 504 deletions
diff --git a/archivers/libarchive/files/doc/html/Makefile b/archivers/libarchive/files/doc/html/Makefile index e045e7c3ffa..5fdc652f049 100644 --- a/archivers/libarchive/files/doc/html/Makefile +++ b/archivers/libarchive/files/doc/html/Makefile @@ -11,6 +11,9 @@ archive_entry_acl.3.html: ../../libarchive/archive_entry_acl.3 archive_entry_linkify.3.html: ../../libarchive/archive_entry_linkify.3 groff -mdoc -T html ../../libarchive/archive_entry_linkify.3 > archive_entry_linkify.3.html +archive_entry_misc.3.html: ../../libarchive/archive_entry_misc.3 + groff -mdoc -T html ../../libarchive/archive_entry_misc.3 > archive_entry_misc.3.html + archive_entry_paths.3.html: ../../libarchive/archive_entry_paths.3 groff -mdoc -T html ../../libarchive/archive_entry_paths.3 > archive_entry_paths.3.html @@ -127,4 +130,4 @@ bsdtar.1.html: ../../tar/bsdtar.1 bsdcpio.1.html: ../../cpio/bsdcpio.1 groff -mdoc -T html ../../cpio/bsdcpio.1 > bsdcpio.1.html -all: archive_entry.3.html archive_entry_acl.3.html archive_entry_linkify.3.html archive_entry_paths.3.html archive_entry_perms.3.html archive_entry_stat.3.html archive_entry_time.3.html archive_read.3.html archive_read_add_passphrase.3.html archive_read_data.3.html archive_read_disk.3.html archive_read_extract.3.html archive_read_filter.3.html archive_read_format.3.html archive_read_free.3.html archive_read_header.3.html archive_read_new.3.html archive_read_open.3.html archive_read_set_options.3.html archive_util.3.html archive_write.3.html archive_write_blocksize.3.html archive_write_data.3.html archive_write_disk.3.html archive_write_filter.3.html archive_write_finish_entry.3.html archive_write_format.3.html archive_write_free.3.html archive_write_header.3.html archive_write_new.3.html archive_write_open.3.html archive_write_set_options.3.html archive_write_set_passphrase.3.html cpio.5.html libarchive.3.html libarchive_changes.3.html libarchive-formats.5.html libarchive_internals.3.html mtree.5.html tar.5.html bsdtar.1.html bsdcpio.1.html +all: archive_entry.3.html archive_entry_acl.3.html archive_entry_linkify.3.html archive_entry_misc.3.html archive_entry_paths.3.html archive_entry_perms.3.html archive_entry_stat.3.html archive_entry_time.3.html archive_read.3.html archive_read_add_passphrase.3.html archive_read_data.3.html archive_read_disk.3.html archive_read_extract.3.html archive_read_filter.3.html archive_read_format.3.html archive_read_free.3.html archive_read_header.3.html archive_read_new.3.html archive_read_open.3.html archive_read_set_options.3.html archive_util.3.html archive_write.3.html archive_write_blocksize.3.html archive_write_data.3.html archive_write_disk.3.html archive_write_filter.3.html archive_write_finish_entry.3.html archive_write_format.3.html archive_write_free.3.html archive_write_header.3.html archive_write_new.3.html archive_write_open.3.html archive_write_set_options.3.html archive_write_set_passphrase.3.html cpio.5.html libarchive.3.html libarchive_changes.3.html libarchive-formats.5.html libarchive_internals.3.html mtree.5.html tar.5.html bsdtar.1.html bsdcpio.1.html diff --git a/archivers/libarchive/files/doc/html/archive_entry.3.html b/archivers/libarchive/files/doc/html/archive_entry.3.html index 7833e8b8c55..19de7283adc 100644 --- a/archivers/libarchive/files/doc/html/archive_entry.3.html +++ b/archivers/libarchive/files/doc/html/archive_entry.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:06 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:14 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_entry_acl.3.html b/archivers/libarchive/files/doc/html/archive_entry_acl.3.html index e87c56679e0..a4465f2bf94 100644 --- a/archivers/libarchive/files/doc/html/archive_entry_acl.3.html +++ b/archivers/libarchive/files/doc/html/archive_entry_acl.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:07 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:14 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -137,12 +137,12 @@ descriptions</p> <p style="margin-top: 1em"><b>DESCRIPTION</b></p> -<p style="margin-left:6%;">The ’’Access Control -Lists (ACLs)’’ extend the standard Unix perssion -model. The ACL interface of <b>libarchive</b> supports both -POSIX.1e and NFSv4 style ACLs. Use of ACLs is restricted by -various levels of ACL support in operating systems, file -systems and archive formats.</p> +<p style="margin-left:6%;">The “Access Control Lists +(ACLs)” extend the standard Unix perssion model. The +ACL interface of <b>libarchive</b> supports both POSIX.1e +and NFSv4 style ACLs. Use of ACLs is restricted by various +levels of ACL support in operating systems, file systems and +archive formats.</p> <p style="margin-left:6%; margin-top: 1em"><b>POSIX.1e Access Control Lists</b> <br> @@ -440,11 +440,11 @@ formats that can be created with <b>archive_entry_acl_to_text_w</b>(). Existing ACL entries are preserved. To get a clean new ACL from text <b>archive_entry_acl_clear</b>() must be called first. -Entries prefixed with ’’default:’’ -are treated as ARCHIVE_ENTRY_ACL_TYPE_DEFAULT unless -<i>type</i> is ARCHIVE_ENTRY_ACL_TYPE_NFS4. Invalid entries, -non-parseable ACL entries and entries beginning with the -’#’ character (comments) are skipped.</p> +Entries prefixed with “default:” are treated as +ARCHIVE_ENTRY_ACL_TYPE_DEFAULT unless <i>type</i> is +ARCHIVE_ENTRY_ACL_TYPE_NFS4. Invalid entries, non-parseable +ACL entries and entries beginning with the ’#’ +character (comments) are skipped.</p> <p style="margin-left:6%; margin-top: 1em"><b>archive_entry_acl_next</b>() @@ -489,7 +489,7 @@ ACLs.</p> <p>ARCHIVE_ENTRY_ACL_STYLE_MARK_DEFAULT</p> <p style="margin-left:24%;">Prefix each default ACL entry -with the word ’’default:’’.</p> +with the word “default:”.</p> <p>ARCHIVE_ENTRY_ACL_STYLE_SOLARIS</p> @@ -524,7 +524,7 @@ returned. It the entry contains POSIX.1e ACLs and none of the flags ARCHIVE_ENTRY_ACL_TYPE_ACCESS or ARCHIVE_ENTRY_ACL_TYPE_DEFAULT are specified, both access and default entries are returned and default entries are -prefixed with ’’default:’’.</p> +prefixed with “default:”.</p> <p style="margin-left:6%; margin-top: 1em"><b>archive_entry_acl_types</b>() diff --git a/archivers/libarchive/files/doc/html/archive_entry_linkify.3.html b/archivers/libarchive/files/doc/html/archive_entry_linkify.3.html index 5e9d077563a..4ee95ca5a0b 100644 --- a/archivers/libarchive/files/doc/html/archive_entry_linkify.3.html +++ b/archivers/libarchive/files/doc/html/archive_entry_linkify.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:07 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:15 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_entry_misc.3.html b/archivers/libarchive/files/doc/html/archive_entry_misc.3.html new file mode 100644 index 00000000000..c41b3339957 --- /dev/null +++ b/archivers/libarchive/files/doc/html/archive_entry_misc.3.html @@ -0,0 +1,91 @@ +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:15 2019 --> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" +"http://www.w3.org/TR/html4/loose.dtd"> +<html> +<head> +<meta name="generator" content="groff -Thtml, see www.gnu.org"> +<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII"> +<meta name="Content-Style" content="text/css"> +<style type="text/css"> + p { margin-top: 0; margin-bottom: 0; vertical-align: top } + pre { margin-top: 0; margin-bottom: 0; vertical-align: top } + table { margin-top: 0; margin-bottom: 0; vertical-align: top } + h1 { text-align: center } +</style> +<title></title> +</head> +<body> + +<hr> + + +<p>ARCHIVE_ENTRY_MISC(3) BSD Library Functions Manual +ARCHIVE_ENTRY_MISC(3)</p> + +<p style="margin-top: 1em"><b>NAME</b></p> + + +<p style="margin-left:6%;"><b>archive_entry_symlink_type</b>, +<b>archive_entry_set_symlink_type</b> — miscellaneous +functions for manipulating properties of archive_entry.</p> + +<p style="margin-top: 1em"><b>LIBRARY</b></p> + +<p style="margin-left:6%;">Streaming Archive Library +(libarchive, -larchive)</p> + +<p style="margin-top: 1em"><b>SYNOPSIS</b></p> + +<p style="margin-left:6%;"><b>#include +<archive_entry.h></b></p> + +<p style="margin-left:6%; margin-top: 1em"><i>int</i></p> + + +<p style="margin-left:12%;"><b>archive_entry_symlink_type</b>(<i>struct archive_entry *a</i>);</p> + +<p style="margin-left:6%; margin-top: 1em"><i>void</i></p> + + +<p style="margin-left:12%;"><b>archive_entry_set_symlink_type</b>(<i>struct archive_entry *a</i>, +<i>int</i>);</p> + +<p style="margin-top: 1em"><b>DESCRIPTION</b></p> + +<p style="margin-left:6%;">The function +<b>archive_entry_symlink_type</b>() returns and the function +<b>archive_entry_set_symlink_type</b>() sets the type of the +symbolic link stored in an archive entry. These functions +have special meaning on operating systems that support +multiple symbolic link types (e.g. Microsoft Windows).</p> + +<p style="margin-left:6%; margin-top: 1em">Supported values +are:</p> + +<p>AE_SYMLINK_TYPE_UNDEFINED</p> + +<p style="margin-left:41%; margin-top: 1em">Symbolic link +target type is not defined (default on unix systems)</p> + +<p>AE_SYMLINK_TYPE_FILE</p> + +<p style="margin-left:41%; margin-top: 1em">Symbolic link +points to a file</p> + +<p>AE_SYMLINK_TYPE_DIRECTORY</p> + +<p style="margin-left:41%; margin-top: 1em">Symbolic link +points to a directory</p> + +<p style="margin-top: 1em"><b>SEE ALSO</b></p> + +<p style="margin-left:6%;">archive_entry(3), +archive_entry_paths(3), archive_entry_stat(3), +libarchive(3)</p> + +<p style="margin-left:6%; margin-top: 1em">BSD +April 15, 2019 BSD</p> +<hr> +</body> +</html> diff --git a/archivers/libarchive/files/doc/html/archive_entry_paths.3.html b/archivers/libarchive/files/doc/html/archive_entry_paths.3.html index 252bdbfbea4..0e1c23598e3 100644 --- a/archivers/libarchive/files/doc/html/archive_entry_paths.3.html +++ b/archivers/libarchive/files/doc/html/archive_entry_paths.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:07 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:15 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_entry_perms.3.html b/archivers/libarchive/files/doc/html/archive_entry_perms.3.html index df9b1cd8482..ebb537c1e3a 100644 --- a/archivers/libarchive/files/doc/html/archive_entry_perms.3.html +++ b/archivers/libarchive/files/doc/html/archive_entry_perms.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:07 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:15 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_entry_stat.3.html b/archivers/libarchive/files/doc/html/archive_entry_stat.3.html index 4f6c0659db8..3a5d88ecade 100644 --- a/archivers/libarchive/files/doc/html/archive_entry_stat.3.html +++ b/archivers/libarchive/files/doc/html/archive_entry_stat.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:07 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:15 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_entry_time.3.html b/archivers/libarchive/files/doc/html/archive_entry_time.3.html index f8e5a1e52b4..0087fd320f2 100644 --- a/archivers/libarchive/files/doc/html/archive_entry_time.3.html +++ b/archivers/libarchive/files/doc/html/archive_entry_time.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:07 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:15 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_read.3.html b/archivers/libarchive/files/doc/html/archive_read.3.html index cd642769a7a..3a9cb6abedc 100644 --- a/archivers/libarchive/files/doc/html/archive_read.3.html +++ b/archivers/libarchive/files/doc/html/archive_read.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:07 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:15 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -224,7 +224,7 @@ example, many implementations of tar(1) allow you to append entries to an empty file. Of course, it is impossible to determine the format of an empty file by inspecting the contents, so this library treats empty files as having a -special ’’empty’’ format.</p> +special “empty” format.</p> <p style="margin-left:6%; margin-top: 1em">BSD February 2, 2012 BSD</p> diff --git a/archivers/libarchive/files/doc/html/archive_read_add_passphrase.3.html b/archivers/libarchive/files/doc/html/archive_read_add_passphrase.3.html index c0b5f69e07c..135b89058a2 100644 --- a/archivers/libarchive/files/doc/html/archive_read_add_passphrase.3.html +++ b/archivers/libarchive/files/doc/html/archive_read_add_passphrase.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:07 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:15 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_read_data.3.html b/archivers/libarchive/files/doc/html/archive_read_data.3.html index 126d8431312..81e2603531a 100644 --- a/archivers/libarchive/files/doc/html/archive_read_data.3.html +++ b/archivers/libarchive/files/doc/html/archive_read_data.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:07 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:15 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_read_disk.3.html b/archivers/libarchive/files/doc/html/archive_read_disk.3.html index 2847481b332..aec5789a561 100644 --- a/archivers/libarchive/files/doc/html/archive_read_disk.3.html +++ b/archivers/libarchive/files/doc/html/archive_read_disk.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:07 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:16 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -188,13 +188,11 @@ is not restored.</p> <b>archive_read_disk_set_symlink_hybrid</b>()</p> <p style="margin-left:17%;">This sets the mode used for -handling symbolic links. The -’’logical’’ mode follows all -symbolic links. The ’’physical’’ -mode does not follow any symbolic links. The -’’hybrid’’ mode currently behaves -identically to the ’’logical’’ -mode.</p> +handling symbolic links. The “logical” mode +follows all symbolic links. The “physical” mode +does not follow any symbolic links. The “hybrid” +mode currently behaves identically to the +“logical” mode.</p> <p style="margin-top: 1em"><b>archive_read_disk_gname</b>(), @@ -348,11 +346,10 @@ was written by Tim Kientzle <p style="margin-top: 1em"><b>BUGS</b></p> -<p style="margin-left:6%;">The -’’standard’’ user name and group -name lookup functions are not the defaults because -getgrgid(3) and getpwuid(3) are sometimes too large for -particular applications. The current design allows the +<p style="margin-left:6%;">The “standard” user +name and group name lookup functions are not the defaults +because getgrgid(3) and getpwuid(3) are sometimes too large +for particular applications. The current design allows the application author to use a more compact implementation when appropriate.</p> @@ -371,9 +368,8 @@ such information.</p> <p style="margin-left:6%; margin-top: 1em">This API should provide a set of methods for walking a directory tree. That would make it a direct parallel of the archive_read(3) API. -When such methods are implemented, the -’’hybrid’’ symbolic link mode will -make sense.</p> +When such methods are implemented, the “hybrid” +symbolic link mode will make sense.</p> <p style="margin-left:6%; margin-top: 1em">BSD April 3, 2017 BSD</p> diff --git a/archivers/libarchive/files/doc/html/archive_read_extract.3.html b/archivers/libarchive/files/doc/html/archive_read_extract.3.html index 046eece2157..f9ce3d1bbc7 100644 --- a/archivers/libarchive/files/doc/html/archive_read_extract.3.html +++ b/archivers/libarchive/files/doc/html/archive_read_extract.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:08 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:16 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_read_filter.3.html b/archivers/libarchive/files/doc/html/archive_read_filter.3.html index b41a6dcda7d..483d366f071 100644 --- a/archivers/libarchive/files/doc/html/archive_read_filter.3.html +++ b/archivers/libarchive/files/doc/html/archive_read_filter.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:08 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:16 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -156,8 +156,7 @@ functions may fall back on external programs if an appropriate library was not available at build time. Decompression using an external program is usually slower than decompression through built-in libraries. Note that -’’none’’ is always enabled by -default.</p> +“none” is always enabled by default.</p> <p><b>archive_read_support_filter_all</b>()</p> diff --git a/archivers/libarchive/files/doc/html/archive_read_format.3.html b/archivers/libarchive/files/doc/html/archive_read_format.3.html index 81eba00dc9a..e3dd4c5ba0e 100644 --- a/archivers/libarchive/files/doc/html/archive_read_format.3.html +++ b/archivers/libarchive/files/doc/html/archive_read_format.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:08 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:16 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -153,8 +153,8 @@ variants.</p> <p><b>archive_read_support_format_all</b>()</p> <p style="margin-left:17%;">Enables support for all -available formats except the ’’raw’’ -format (see below).</p> +available formats except the “raw” format (see +below).</p> <p><b>archive_read_support_format_by_code</b>()</p> @@ -179,11 +179,10 @@ distinct format.</p> <p><b>archive_read_support_format_raw</b>()</p> -<p style="margin-left:17%;">The -’’raw’’ format handler allows -libarchive to be used to read arbitrary data. It treats any -data stream as an archive with a single entry. The pathname -of this entry is ’’data’’; all other +<p style="margin-left:17%;">The “raw” format +handler allows libarchive to be used to read arbitrary data. +It treats any data stream as an archive with a single entry. +The pathname of this entry is “data”; all other entry fields are unset. This is not enabled by <b>archive_read_support_format_all</b>() in order to avoid erroneous handling of damaged archives.</p> @@ -213,12 +212,11 @@ example, many implementations of tar(1) allow you to append entries to an empty file. Of course, it is impossible to determine the format of an empty file by inspecting the contents, so this library treats empty files as having a -special ’’empty’’ format.</p> +special “empty” format.</p> <p style="margin-left:6%; margin-top: 1em">Using the -’’raw’’ handler together with any -other handler will often work but can produce surprising -results.</p> +“raw” handler together with any other handler +will often work but can produce surprising results.</p> <p style="margin-left:6%; margin-top: 1em">BSD February 2, 2012 BSD</p> diff --git a/archivers/libarchive/files/doc/html/archive_read_free.3.html b/archivers/libarchive/files/doc/html/archive_read_free.3.html index 16c8b4838db..3005db7bd43 100644 --- a/archivers/libarchive/files/doc/html/archive_read_free.3.html +++ b/archivers/libarchive/files/doc/html/archive_read_free.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:08 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:16 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_read_header.3.html b/archivers/libarchive/files/doc/html/archive_read_header.3.html index 988a46ebee2..a15d4e49b82 100644 --- a/archivers/libarchive/files/doc/html/archive_read_header.3.html +++ b/archivers/libarchive/files/doc/html/archive_read_header.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:08 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:16 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_read_new.3.html b/archivers/libarchive/files/doc/html/archive_read_new.3.html index e2078e56504..a44a4c053b6 100644 --- a/archivers/libarchive/files/doc/html/archive_read_new.3.html +++ b/archivers/libarchive/files/doc/html/archive_read_new.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:08 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:16 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_read_open.3.html b/archivers/libarchive/files/doc/html/archive_read_open.3.html index 72d2e8e14bf..200321bc5b7 100644 --- a/archivers/libarchive/files/doc/html/archive_read_open.3.html +++ b/archivers/libarchive/files/doc/html/archive_read_open.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:08 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:16 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_read_set_options.3.html b/archivers/libarchive/files/doc/html/archive_read_set_options.3.html index cff2a0ae3c6..32632e4f6c3 100644 --- a/archivers/libarchive/files/doc/html/archive_read_set_options.3.html +++ b/archivers/libarchive/files/doc/html/archive_read_set_options.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:08 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:16 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -142,7 +142,7 @@ option with this name will ignore it.</p> <p style="margin-left:27%; margin-top: 1em">The option will be provided to every module with a value of -’’1’’.</p> +“1”.</p> <p><i>!option</i></p> diff --git a/archivers/libarchive/files/doc/html/archive_util.3.html b/archivers/libarchive/files/doc/html/archive_util.3.html index be632ffbe92..6aa59b612b6 100644 --- a/archivers/libarchive/files/doc/html/archive_util.3.html +++ b/archivers/libarchive/files/doc/html/archive_util.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:08 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:16 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -253,23 +253,14 @@ This function should be used within I/O callbacks to set system-specific error codes and error descriptions. This function accepts a printf-like format string and arguments. However, you should be careful to use only the following -printf format specifiers: ’’%c’’, -’’%d’’, -’’%jd’’, -’’%jo’’, -’’%ju’’, -’’%jx’’, -’’%ld’’, -’’%lo’’, -’’%lu’’, -’’%lx’’, -’’%o’’, -’’%u’’, -’’%s’’, -’’%x’’, -’’%%’’. Field-width specifiers and -other printf features are not uniformly supported and should -not be used.</p> +printf format specifiers: “%c”, +“%d”, “%jd”, “%jo”, +“%ju”, “%jx”, “%ld”, +“%lo”, “%lu”, “%lx”, +“%o”, “%u”, “%s”, +“%x”, “%%”. Field-width specifiers +and other printf features are not uniformly supported and +should not be used.</p> <p style="margin-top: 1em"><b>SEE ALSO</b></p> diff --git a/archivers/libarchive/files/doc/html/archive_write.3.html b/archivers/libarchive/files/doc/html/archive_write.3.html index e92da664c1a..f3c40a16770 100644 --- a/archivers/libarchive/files/doc/html/archive_write.3.html +++ b/archivers/libarchive/files/doc/html/archive_write.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:08 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:17 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -273,11 +273,11 @@ limitations and provides a generic key/value attribute facility for vendor-defined extensions. One oversight in POSIX is the failure to provide a standard attribute for large device numbers. This library uses -’’SCHILY.devminor’’ and -’’SCHILY.devmajor’’ for device -numbers that exceed the range supported by the -backwards-compatible ustar header. These keys are compatible -with Joerg Schilling’s <b>star</b> archiver. Other +“SCHILY.devminor” and +“SCHILY.devmajor” for device numbers that exceed +the range supported by the backwards-compatible ustar +header. These keys are compatible with Joerg +Schilling’s <b>star</b> archiver. Other implementations may not recognize these keys and will thus be unable to correctly restore device nodes with large device numbers from archives created by this library.</p> diff --git a/archivers/libarchive/files/doc/html/archive_write_blocksize.3.html b/archivers/libarchive/files/doc/html/archive_write_blocksize.3.html index 3d233788518..c0bff216878 100644 --- a/archivers/libarchive/files/doc/html/archive_write_blocksize.3.html +++ b/archivers/libarchive/files/doc/html/archive_write_blocksize.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:08 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:17 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -97,8 +97,8 @@ compression. The uncompressed data is always unpadded. The default is to pad the last block to the full block size (note that <b>archive_write_open_filename</b>() will set this based on the file type). Unlike the other -’’set’’ functions, this function can -be called after the archive is opened.</p> +“set” functions, this function can be called +after the archive is opened.</p> <p style="margin-top: 1em"><b>archive_write_get_bytes_in_last_block</b>()</p> diff --git a/archivers/libarchive/files/doc/html/archive_write_data.3.html b/archivers/libarchive/files/doc/html/archive_write_data.3.html index 0d386fafa0e..93c5716dee6 100644 --- a/archivers/libarchive/files/doc/html/archive_write_data.3.html +++ b/archivers/libarchive/files/doc/html/archive_write_data.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:08 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:17 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_write_disk.3.html b/archivers/libarchive/files/doc/html/archive_write_disk.3.html index d13bbe7b95d..de65dc4fab8 100644 --- a/archivers/libarchive/files/doc/html/archive_write_disk.3.html +++ b/archivers/libarchive/files/doc/html/archive_write_disk.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:09 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:17 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -350,12 +350,11 @@ of the final object happen to match those specified in the entry.</p> <p style="margin-left:6%; margin-top: 1em">The -’’standard’’ user-id and group-id -lookup functions are not the defaults because getgrnam(3) -and getpwnam(3) are sometimes too large for particular -applications. The current design allows the application -author to use a more compact implementation when -appropriate.</p> +“standard” user-id and group-id lookup functions +are not the defaults because getgrnam(3) and getpwnam(3) are +sometimes too large for particular applications. The current +design allows the application author to use a more compact +implementation when appropriate.</p> <p style="margin-left:6%; margin-top: 1em">There should be a corresponding <b>archive_read_disk</b> interface that diff --git a/archivers/libarchive/files/doc/html/archive_write_filter.3.html b/archivers/libarchive/files/doc/html/archive_write_filter.3.html index 6e86d8555bf..be89c6c7e65 100644 --- a/archivers/libarchive/files/doc/html/archive_write_filter.3.html +++ b/archivers/libarchive/files/doc/html/archive_write_filter.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:09 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:17 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_write_finish_entry.3.html b/archivers/libarchive/files/doc/html/archive_write_finish_entry.3.html index bc1f5c6dbeb..91fabf50754 100644 --- a/archivers/libarchive/files/doc/html/archive_write_finish_entry.3.html +++ b/archivers/libarchive/files/doc/html/archive_write_finish_entry.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:09 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:17 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_write_format.3.html b/archivers/libarchive/files/doc/html/archive_write_format.3.html index 44a5cc45101..dad31d1a413 100644 --- a/archivers/libarchive/files/doc/html/archive_write_format.3.html +++ b/archivers/libarchive/files/doc/html/archive_write_format.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:09 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:17 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_write_free.3.html b/archivers/libarchive/files/doc/html/archive_write_free.3.html index 2346fe9e1b7..ff7bdebac63 100644 --- a/archivers/libarchive/files/doc/html/archive_write_free.3.html +++ b/archivers/libarchive/files/doc/html/archive_write_free.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:09 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:17 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_write_header.3.html b/archivers/libarchive/files/doc/html/archive_write_header.3.html index cb538860af5..760bc6d5352 100644 --- a/archivers/libarchive/files/doc/html/archive_write_header.3.html +++ b/archivers/libarchive/files/doc/html/archive_write_header.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:09 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:17 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_write_new.3.html b/archivers/libarchive/files/doc/html/archive_write_new.3.html index fff8510e6c0..2f8436b9831 100644 --- a/archivers/libarchive/files/doc/html/archive_write_new.3.html +++ b/archivers/libarchive/files/doc/html/archive_write_new.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:09 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:17 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_write_open.3.html b/archivers/libarchive/files/doc/html/archive_write_open.3.html index 294f28d75cb..61d787ff372 100644 --- a/archivers/libarchive/files/doc/html/archive_write_open.3.html +++ b/archivers/libarchive/files/doc/html/archive_write_open.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:09 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:17 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -115,9 +115,8 @@ require correct blocking.</p> <p style="margin-left:17%;">A convenience form of <b>archive_write_open</b>() that accepts a filename. A NULL argument indicates that the output should be written to -standard output; an argument of -’’-’’ will open a file with that -name. If you have not invoked +standard output; an argument of “-” will open a +file with that name. If you have not invoked <b>archive_write_set_bytes_in_last_block</b>(), then <b>archive_write_open_filename</b>() will adjust the last-block padding depending on the file: it will enable diff --git a/archivers/libarchive/files/doc/html/archive_write_set_options.3.html b/archivers/libarchive/files/doc/html/archive_write_set_options.3.html index 3239f738af1..1a9bf8ff3ae 100644 --- a/archivers/libarchive/files/doc/html/archive_write_set_options.3.html +++ b/archivers/libarchive/files/doc/html/archive_write_set_options.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:09 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:18 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -138,7 +138,7 @@ option with this name will ignore it.</p> <p style="margin-left:27%; margin-top: 1em">The option will be provided to every module with a value of -’’1’’.</p> +“1”.</p> <p><i>!option</i></p> @@ -175,8 +175,8 @@ cksum</b>, <b>device</b>, <b>flags</b>, <b>gid</b>, <p style="margin-left:27%;">Enable a particular keyword in the mtree output. Prefix with an exclamation mark to disable the corresponding keyword. The default is equivalent to -’’device, flags, gid, gname, link, mode, nlink, -size, time, type, uid, uname’’.</p> +“device, flags, gid, gname, link, mode, nlink, size, +time, type, uid, uname”.</p> <p><b>all</b></p> @@ -483,9 +483,8 @@ compression on many files.</p> compression</b></p> <p style="margin-left:27%;">The value is either -’’store’’ or -’’deflate’’ to indicate how the -following entries should be compressed. Note that this +“store” or “deflate” to indicate how +the following entries should be compressed. Note that this setting is ignored for directories, symbolic links, and other special entries.</p> diff --git a/archivers/libarchive/files/doc/html/archive_write_set_passphrase.3.html b/archivers/libarchive/files/doc/html/archive_write_set_passphrase.3.html index 5012a0b244a..f6c4579b435 100644 --- a/archivers/libarchive/files/doc/html/archive_write_set_passphrase.3.html +++ b/archivers/libarchive/files/doc/html/archive_write_set_passphrase.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:09 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:18 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/bsdcpio.1.html b/archivers/libarchive/files/doc/html/bsdcpio.1.html index 7cfb2712e43..511c4b1b33a 100644 --- a/archivers/libarchive/files/doc/html/bsdcpio.1.html +++ b/archivers/libarchive/files/doc/html/bsdcpio.1.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:11 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:19 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -430,10 +430,9 @@ pattern:</p> <p style="margin-left:6%; margin-top: 1em">This example copies files from <i>src</i> to <i>dest</i> that are more -than 2 days old and which contain the word -’’</p> +than 2 days old and which contain the word “</p> -<p>foobar ’’:</p> +<p>foobar ”:</p> <p style="margin-left:14%;"><b>find</b> <i>src</i> <b>-mtime</b> <i>+2</i> | <b>xargs grep -l foobar</b> | @@ -467,14 +466,12 @@ libarchive-formats(5), tar(5)</p> <p style="margin-left:6%;">There is no current POSIX standard for the cpio command; it appeared in ISO/IEC -9945-1:1996 (’’POSIX.1’’) but was -dropped from IEEE Std 1003.1-2001 -(’’POSIX.1’’).</p> +9945-1:1996 (“POSIX.1”) but was dropped from +IEEE Std 1003.1-2001 (“POSIX.1”).</p> <p style="margin-left:6%; margin-top: 1em">The cpio, ustar, and pax interchange file formats are defined by IEEE Std -1003.1-2001 (’’POSIX.1’’) for the -pax command.</p> +1003.1-2001 (“POSIX.1”) for the pax command.</p> <p style="margin-top: 1em"><b>HISTORY</b></p> @@ -482,12 +479,12 @@ pax command.</p> <b>find</b> utilities were written by Dick Haight while working in AT&T’s Unix Support Group. They first appeared in 1977 in PWB/UNIX 1.0, the -’’Programmer’s Work Bench’’ -system developed for use within AT&T. They were first -released outside of AT&T as part of System III Unix in -1981. As a result, <b>cpio</b> actually predates <b>tar</b>, -even though it was not well-known outside of AT&T until -some time later.</p> +“Programmer’s Work Bench” system developed +for use within AT&T. They were first released outside of +AT&T as part of System III Unix in 1981. As a result, +<b>cpio</b> actually predates <b>tar</b>, even though it was +not well-known outside of AT&T until some time +later.</p> <p style="margin-left:6%; margin-top: 1em">This is a complete re-implementation based on the libarchive(3) @@ -502,8 +499,8 @@ to transfer files between systems with dissimilar user and group numbering. Older cpio formats limit the user and group numbers to 16 or 18 bits, which is insufficient for modern systems. The cpio archive formats cannot support files over -4 gigabytes, except for the ’’odc’’ -variant, which can support files up to 8 gigabytes.</p> +4 gigabytes, except for the “odc” variant, which +can support files up to 8 gigabytes.</p> <p style="margin-left:6%; margin-top: 1em">BSD September 16, 2014 BSD</p> diff --git a/archivers/libarchive/files/doc/html/bsdtar.1.html b/archivers/libarchive/files/doc/html/bsdtar.1.html index ff7e6de0b15..8f42def5aad 100644 --- a/archivers/libarchive/files/doc/html/bsdtar.1.html +++ b/archivers/libarchive/files/doc/html/bsdtar.1.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:11 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:19 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -54,10 +54,9 @@ and ISO 9660 cdrom images and can create tar, pax, cpio, ar, zip, 7-zip, and shar archives.</p> <p style="margin-left:6%; margin-top: 1em">The first -synopsis form shows a ’’bundled’’ -option word. This usage is provided for compatibility with -historical implementations. See COMPATIBILITY below for -details.</p> +synopsis form shows a “bundled” option word. +This usage is provided for compatibility with historical +implementations. See COMPATIBILITY below for details.</p> <p style="margin-left:6%; margin-top: 1em">The other synopsis forms show the preferred usage. The first option to @@ -176,9 +175,9 @@ format,</p> <p style="margin-left:24%;"><b>tar -a -jcf</b> <i>archive.tgz source.c source.h</i></p> -<p style="margin-left:17%;">ignores the -’’-j’’ option, and creates a new -archive with restricted pax format and gzip compression,</p> +<p style="margin-left:17%;">ignores the “-j” +option, and creates a new archive with restricted pax format +and gzip compression,</p> <p style="margin-left:24%;"><b>tar -a -jcf</b> <i>archive.xxx source.c source.h</i></p> @@ -232,7 +231,8 @@ options and before extracting any files.</p> <p style="margin-left:17%;">(x mode only) Before removing file system objects to replace them, clear platform-specific -file flags that might prevent removal.</p> +file attributes or file flags that might prevent +removal.</p> <p style="margin-top: 1em"><b>--exclude</b> <i>pattern</i></p> @@ -242,27 +242,34 @@ directories that match the specified pattern. Note that exclusions take precedence over patterns or filenames specified on the command line.</p> +<p style="margin-top: 1em"><b>--exclude-vcs</b></p> + +<p style="margin-left:17%;">Do not process files or +directories internally used by the version control systems +’CVS’, ’RCS’, ’SCCS’, +’SVN’, ’Arch’, ’Bazaar’, +’Mercurial’ and ’Darcs’.</p> + <p style="margin-top: 1em"><b>--fflags</b></p> <p style="margin-left:17%;">(c, r, u, x modes only) Archive -or extract file flags. This is the reverse of -<b>--no-fflags</b> and the default behavior in c, r, and u -modes or if <b>tar</b> is run in x mode as root.</p> +or extract platform-specific file attributes or file flags. +This is the reverse of <b>--no-fflags</b> and the default +behavior in c, r, and u modes or if <b>tar</b> is run in x +mode as root.</p> <p style="margin-top: 1em"><b>--format</b> <i>format</i></p> <p style="margin-left:17%;">(c, r, u mode only) Use the specified format for the created archive. Supported formats -include ’’cpio’’, -’’pax’’, -’’shar’’, and -’’ustar’’. Other formats may also be -supported; see libarchive-formats(5) for more information -about currently-supported formats. In r and u modes, when -extending an existing archive, the format specified here -must be compatible with the format of the existing archive -on disk.</p> +include “cpio”, “pax”, +“shar”, and “ustar”. Other formats +may also be supported; see libarchive-formats(5) for more +information about currently-supported formats. In r and u +modes, when extending an existing archive, the format +specified here must be compatible with the format of the +existing archive on disk.</p> <p style="margin-top: 1em"><b>-f</b> <i>file</i>, <b>--file</b> <i>file</i></p> @@ -443,16 +450,16 @@ to the time stored in the archive.</p> <p style="margin-left:17%;">(c, r, u and x mode only) Mac OS X specific. Archive or extract extended ACLs and extended -attributes using copyfile(3) in AppleDouble format. This is -the reverse of <b>--no-mac-metadata</b>. and the default -behavior in c, r, and u modes or if <b>tar</b> is run in x -mode as root.</p> +file attributes using copyfile(3) in AppleDouble format. +This is the reverse of <b>--no-mac-metadata</b>. and the +default behavior in c, r, and u modes or if <b>tar</b> is +run in x mode as root.</p> <p style="margin-top: 1em"><b>-n</b>, <b>--norecurse</b>, <b>--no-recursion</b></p> -<p style="margin-left:17%;">(c, r, u modes only) Do not -recursively archive the contents of directories.</p> +<p style="margin-left:17%;">Do not operate recursively on +the content of directories.</p> <p style="margin-top: 1em"><b>--newer</b> <i>date</i></p> @@ -514,21 +521,18 @@ user in c, r, u and x modes).</p> <p style="margin-top: 1em"><b>--no-fflags</b></p> <p style="margin-left:17%;">(c, r, u, x modes only) Do not -archive or extract file flags. This is the reverse of -<b>--fflags</b> and the default behavior if <b>tar</b> is -run as non-root in x mode.</p> +archive or extract file attributes or file flags. This is +the reverse of <b>--fflags</b> and the default behavior if +<b>tar</b> is run as non-root in x mode.</p> <p style="margin-top: 1em"><b>--no-mac-metadata</b></p> <p style="margin-left:17%;">(x mode only) Mac OS X -specific. Do not archive or extract ACLs and extended +specific. Do not archive or extract ACLs and extended file attributes using copyfile(3) in AppleDouble format. This is the reverse of <b>--mac-metadata</b>. and the default behavior if <b>tar</b> is run as non-root in x mode.</p> -<p style="margin-top: 1em"><b>-n</b>, <b>--norecurse</b>, -<b>--no-recursion</b></p> - <p style="margin-top: 1em"><b>--no-same-owner</b></p> <p style="margin-left:17%;">(x mode only) Do not extract @@ -540,17 +544,17 @@ is run as non-root.</p> <p style="margin-top: 1em"><b>--no-same-permissions</b></p> <p style="margin-left:17%;">(x mode only) Do not extract -full permissions (SGID, SUID, sticky bit, ACLs, extended -attributes or extended file flags). This is the reverse of -<b>-p</b> and the default behavior if <b>tar</b> is run as -non-root.</p> +full permissions (SGID, SUID, sticky bit, file attributes or +file flags, extended file attributes and ACLs). This is the +reverse of <b>-p</b> and the default behavior if <b>tar</b> +is run as non-root.</p> <p style="margin-top: 1em"><b>--no-xattrs</b></p> <p style="margin-left:17%;">(c, r, u, x modes only) Do not -archive or extract extended attributes. This is the reverse -of <b>--xattrs</b> and the default behavior if <b>tar</b> is -run as non-root in x mode.</p> +archive or extract extended file attributes. This is the +reverse of <b>--xattrs</b> and the default behavior if +<b>tar</b> is run as non-root in x mode.</p> <p style="margin-top: 1em"><b>--numeric-owner</b></p> @@ -739,8 +743,8 @@ output. Supported keywords include: <b>cksum</b>, <b>nlink</b>, <b>rmd160</b>, <b>sha1</b>, <b>sha256</b>, <b>sha384</b>, <b>sha512</b>, <b>size</b>, <b>time</b>, <b>uid</b>, <b>uname</b>. The default is equivalent to: -’’device, flags, gid, gname, link, mode, nlink, -size, time, type, uid, uname’’.</p> +“device, flags, gid, gname, link, mode, nlink, size, +time, type, uid, uname”.</p> <p><b>mtree:all</b></p> @@ -805,11 +809,11 @@ option suppresses these behaviors.</p> <p style="margin-left:17%;">(x mode only) Preserve file permissions. Attempt to restore the full permissions, -including owner, file modes, ACLs, extended attributes and -extended file flags, if available, for each item extracted -from the archive. This is te reverse of +including file modes, file attributes or file flags, +extended file attributes and ACLs, if available, for each +item extracted from the archive. This is the reverse of <b>--no-same-permissions</b> and the default if <b>tar</b> -is being run by root and can be partially overridden by also +is being run as root. It can be partially overridden by also specifying <b>--no-acls</b>, <b>--no-fflags</b>, <b>--no-mac-metadata</b> or <b>--no-xattrs</b>.</p> @@ -894,13 +898,12 @@ checks.</p> <p style="margin-left:17%;">In x or t mode, <b>tar</b> will read the list of names to be extracted from <i>filename</i>. In c mode, <b>tar</b> will read names to be archived from -<i>filename</i>. The special name -’’-C’’ on a line by itself will -cause the current directory to be changed to the directory -specified on the following line. Names are terminated by -newlines unless <b>--null</b> is specified. Note that -<b>--null</b> also disables the special handling of lines -containing ’’-C’’. Note: If you are +<i>filename</i>. The special name “-C” on a line +by itself will cause the current directory to be changed to +the directory specified on the following line. Names are +terminated by newlines unless <b>--null</b> is specified. +Note that <b>--null</b> also disables the special handling +of lines containing “-C”. Note: If you are generating lists of files using find(1), you probably want to use <b>-n</b> as well.</p> @@ -974,7 +977,7 @@ more information about the handling of exclusions.</p> <p style="margin-top: 1em"><b>--xattrs</b></p> <p style="margin-left:17%;">(c, r, u, x modes only) Archive -or extract extended attributes. This is the reverse of +or extract extended file attributes. This is the reverse of <b>--no-xattrs</b> and the default behavior in c, r, and u modes or if <b>tar</b> is run in x mode as root.</p> @@ -1118,10 +1121,9 @@ $ tar -cvf output.tar @input.mtree</p> <p style="margin-left:6%; margin-top: 1em">The <b>--newer</b> and <b>--newer-mtime</b> switches accept a variety of common date and time specifications, including -’’12 Mar 2005 7:14:29pm’’, -’’2005-03-12 19:14’’, -’’5 minutes ago’’, and -’’19:14 PST May 1’’.</p> +“12 Mar 2005 7:14:29pm”, “2005-03-12 +19:14”, “5 minutes ago”, and “19:14 +PST May 1”.</p> <p style="margin-left:6%; margin-top: 1em">The <b>--options</b> argument can be used to control various @@ -1249,18 +1251,16 @@ libarchive-formats(5), tar(5)</p> <p style="margin-left:6%;">There is no current POSIX standard for the tar command; it appeared in ISO/IEC -9945-1:1996 (’’POSIX.1’’) but was -dropped from IEEE Std 1003.1-2001 -(’’POSIX.1’’). The options supported -by this implementation were developed by surveying a number -of existing tar implementations as well as the old POSIX -specification for tar and the current POSIX specification -for pax.</p> +9945-1:1996 (“POSIX.1”) but was dropped from +IEEE Std 1003.1-2001 (“POSIX.1”). The options +supported by this implementation were developed by surveying +a number of existing tar implementations as well as the old +POSIX specification for tar and the current POSIX +specification for pax.</p> <p style="margin-left:6%; margin-top: 1em">The ustar and pax interchange file formats are defined by IEEE Std -1003.1-2001 (’’POSIX.1’’) for the -pax command.</p> +1003.1-2001 (“POSIX.1”) for the pax command.</p> <p style="margin-top: 1em"><b>HISTORY</b></p> @@ -1281,9 +1281,9 @@ library. It was first released with FreeBSD 5.4 in May, <p style="margin-top: 1em"><b>BUGS</b></p> <p style="margin-left:6%;">This program follows ISO/IEC -9945-1:1996 (’’POSIX.1’’) for the -definition of the <b>-l</b> option. Note that GNU tar prior -to version 1.15 treated <b>-l</b> as a synonym for the +9945-1:1996 (“POSIX.1”) for the definition of +the <b>-l</b> option. Note that GNU tar prior to version +1.15 treated <b>-l</b> as a synonym for the <b>--one-file-system</b> option.</p> <p style="margin-left:6%; margin-top: 1em">The <b>-C</b> @@ -1349,8 +1349,8 @@ information to be lost. (This is a consequence of the incompatible ways that different archive formats store hardlink information.)</p> -<p style="margin-left:6%; margin-top: 1em">BSD -October 1, 2017 BSD</p> +<p style="margin-left:6%; margin-top: 1em">BSD June 3, +2019 BSD</p> <hr> </body> </html> diff --git a/archivers/libarchive/files/doc/html/cpio.5.html b/archivers/libarchive/files/doc/html/cpio.5.html index 5ee99fd8f27..b699e623232 100644 --- a/archivers/libarchive/files/doc/html/cpio.5.html +++ b/archivers/libarchive/files/doc/html/cpio.5.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:09 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:18 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -46,7 +46,7 @@ those integers (binary, octal, or hexadecimal). The header is followed by the pathname of the entry (the length of the pathname is stored in the header) and any file data. The end of the archive is indicated by a special record with the -pathname ’’TRAILER!!!’’.</p> +pathname “TRAILER!!!”.</p> <p style="margin-left:6%; margin-top: 1em"><b>PWB format</b> <br> @@ -239,13 +239,12 @@ included with each copy of the file.</p> <p style="margin-left:6%; margin-top: 1em"><b>Portable ASCII Format</b> <br> Version 2 of the Single UNIX Specification -(’’SUSv2’’) standardized an ASCII -variant that is portable across all platforms. It is -commonly known as the ’’old -character’’ format or as the -’’odc’’ format. It stores the same -numeric fields as the old binary format, but represents them -as 6-character or 11-character octal values.</p> +(“SUSv2”) standardized an ASCII variant that is +portable across all platforms. It is commonly known as the +“old character” format or as the +“odc” format. It stores the same numeric fields +as the old binary format, but represents them as 6-character +or 11-character octal values.</p> <p style="margin-left:14%; margin-top: 1em">struct cpio_odc_header { <br> @@ -302,7 +301,7 @@ the old binary format above.</p> <p style="margin-top: 1em"><i>magic</i></p> <p style="margin-left:17%; margin-top: 1em">The string -’’070701’’.</p> +“070701”.</p> <p style="margin-top: 1em"><i>check</i></p> @@ -326,11 +325,11 @@ archive.</p> Format</b> <br> The CRC format is identical to the new ASCII format described in the previous section except that the magic -field is set to ’’070702’’ and the -<i>check</i> field is set to the sum of all bytes in the -file data. This sum is computed treating all bytes as -unsigned values and using unsigned arithmetic. Only the -least-significant 32 bits of the sum are stored.</p> +field is set to “070702” and the <i>check</i> +field is set to the sum of all bytes in the file data. This +sum is computed treating all bytes as unsigned values and +using unsigned arithmetic. Only the least-significant 32 +bits of the sum are stored.</p> <p style="margin-left:6%; margin-top: 1em"><b>HP variants</b> <br> @@ -355,34 +354,31 @@ XXX</p> <p style="margin-left:6%;">The <b>cpio</b> utility is no longer a part of POSIX or the Single Unix Standard. It last appeared in Version 2 of the Single UNIX Specification -(’’SUSv2’’). It has been supplanted -in subsequent standards by pax(1). The portable ASCII format -is currently part of the specification for the pax(1) -utility.</p> +(“SUSv2”). It has been supplanted in subsequent +standards by pax(1). The portable ASCII format is currently +part of the specification for the pax(1) utility.</p> <p style="margin-top: 1em"><b>HISTORY</b></p> <p style="margin-left:6%;">The original cpio utility was written by Dick Haight while working in AT&T’s Unix Support Group. It appeared in 1977 as part of PWB/UNIX -1.0, the ’’Programmer’s Work -Bench’’ derived from Version 6 AT&T -UNIX that was used internally at AT&T. Both the old -binary and old character formats were in use by 1980, -according to the System III source released by SCO under -their ’’Ancient Unix’’ license. The -character format was adopted as part of IEEE Std 1003.1-1988 -(’’POSIX.1’’). XXX when did +1.0, the “Programmer’s Work Bench” derived +from Version 6 AT&T UNIX that was used internally +at AT&T. Both the old binary and old character formats +were in use by 1980, according to the System III source +released by SCO under their “Ancient Unix” +license. The character format was adopted as part of IEEE +Std 1003.1-1988 (“POSIX.1”). XXX when did "newc" appear? Who invented it? When did HP come out with their variant? When did Sun introduce ACLs and extended attributes? XXX</p> <p style="margin-top: 1em"><b>BUGS</b></p> -<p style="margin-left:6%;">The -’’CRC’’ format is mis-named, as it -uses a simple checksum and not a cyclic redundancy -check.</p> +<p style="margin-left:6%;">The “CRC” format is +mis-named, as it uses a simple checksum and not a cyclic +redundancy check.</p> <p style="margin-left:6%; margin-top: 1em">The old binary format is limited to 16 bits for user id, group id, device, diff --git a/archivers/libarchive/files/doc/html/libarchive-formats.5.html b/archivers/libarchive/files/doc/html/libarchive-formats.5.html index 6172fea963c..e8a16215526 100644 --- a/archivers/libarchive/files/doc/html/libarchive-formats.5.html +++ b/archivers/libarchive/files/doc/html/libarchive-formats.5.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:10 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:18 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -34,9 +34,9 @@ library</p> <p style="margin-left:6%;">The libarchive(3) library reads and writes a variety of streaming archive formats. Generally speaking, all of these archive formats consist of a series -of ’’entries’’. Each entry stores a -single file system object, such as a file, directory, or -symbolic link.</p> +of “entries”. Each entry stores a single file +system object, such as a file, directory, or symbolic +link.</p> <p style="margin-left:6%; margin-top: 1em">The following provides a brief description of each format supported by @@ -52,10 +52,9 @@ all supported formats.</p> <p style="margin-left:6%; margin-top: 1em"><b>Tar Formats</b> <br> The libarchive(3) library can read most tar archives. It can -write POSIX-standard ’’ustar’’ and -’’pax interchange’’ formats as well -as v7 tar format and a subset of the legacy GNU tar -format.</p> +write POSIX-standard “ustar” and “pax +interchange” formats as well as v7 tar format and a +subset of the legacy GNU tar format.</p> <p style="margin-left:6%; margin-top: 1em">All tar formats store each entry in one or more 512-byte records. The first @@ -99,11 +98,10 @@ standard are in all lowercase; vendors are allowed to define custom keys by preceding them with the vendor name in all uppercase. When writing pax archives, libarchive uses many of the SCHILY keys defined by Joerg Schilling’s -’’star’’ archiver and a few -LIBARCHIVE keys. The libarchive library can read most of the -SCHILY keys and most of the GNU keys introduced by GNU tar. -It silently ignores any keywords that it does not -understand.</p> +“star” archiver and a few LIBARCHIVE keys. The +libarchive library can read most of the SCHILY keys and most +of the GNU keys introduced by GNU tar. It silently ignores +any keywords that it does not understand.</p> <p style="margin-left:17%; margin-top: 1em">The pax interchange format converts filenames to Unicode and stores @@ -241,18 +239,17 @@ extended attribute records written by Solaris tar.</p> <p style="margin-left:6%; margin-top: 1em">The first tar program appeared in Seventh Edition Unix in 1979. The first official standard for the tar file format was the -’’ustar’’ (Unix Standard Tar) format -defined by POSIX in 1988. POSIX.1-2001 extended the ustar -format to create the ’’pax -interchange’’ format.</p> +“ustar” (Unix Standard Tar) format defined by +POSIX in 1988. POSIX.1-2001 extended the ustar format to +create the “pax interchange” format.</p> <p style="margin-left:6%; margin-top: 1em"><b>Cpio Formats</b> <br> The libarchive library can read a number of common cpio -variants and can write ’’odc’’ and -’’newc’’ format archives. A cpio -archive stores each entry as a fixed-size header followed by -a variable-length filename and variable-length data. Unlike +variants and can write “odc” and +“newc” format archives. A cpio archive stores +each entry as a fixed-size header followed by a +variable-length filename and variable-length data. Unlike the tar format, the cpio format does only minimal padding of the header or file data. There are several cpio variants, which differ primarily in how they store the initial header: @@ -272,15 +269,14 @@ mtime, and 16-bit binary values for the other fields.</p> <p style="margin-left:17%; margin-top: 1em">The libarchive library can both read and write this POSIX-standard format, -which is officially known as the ’’cpio -interchange format’’ or the -’’octet-oriented cpio archive -format’’ and sometimes unofficially referred to -as the ’’old character format’’. -This format stores the header contents as octal values in -ASCII. It is standard, portable, and immune from byte-order -confusion. File sizes and mtime are limited to 33 bits (8GB -file size), other fields are limited to 18 bits.</p> +which is officially known as the “cpio interchange +format” or the “octet-oriented cpio archive +format” and sometimes unofficially referred to as the +“old character format”. This format stores the +header contents as octal values in ASCII. It is standard, +portable, and immune from byte-order confusion. File sizes +and mtime are limited to 33 bits (8GB file size), other +fields are limited to 18 bits.</p> <p style="margin-top: 1em"><b>SVR4/newc</b></p> @@ -312,10 +308,10 @@ systems with dissimilar user numbering.</p> <p style="margin-left:6%; margin-top: 1em"><b>Shar Formats</b> <br> -A ’’shell archive’’ is a shell -script that, when executed on a POSIX-compliant system, will -recreate a collection of file system objects. The libarchive -library can write two different kinds of shar archives:</p> +A “shell archive” is a shell script that, when +executed on a POSIX-compliant system, will recreate a +collection of file system objects. The libarchive library +can write two different kinds of shar archives:</p> <p style="margin-top: 1em"><b>shar</b></p> @@ -379,15 +375,15 @@ variables.</p> format</b> <br> Libarchive can read and write zip format archives that have uncompressed entries and entries compressed with the -’’deflate’’ algorithm. Other zip -compression algorithms are not supported. It can extract jar -archives, archives that use Zip64 extensions and -self-extracting zip archives. Libarchive can use either of -two different strategies for reading Zip archives: a -streaming strategy which is fast and can handle extremely -large archives, and a seeking strategy which can correctly -process self-extracting Zip archives and archives with -deleted members or other in-place modifications.</p> +“deflate” algorithm. Other zip compression +algorithms are not supported. It can extract jar archives, +archives that use Zip64 extensions and self-extracting zip +archives. Libarchive can use either of two different +strategies for reading Zip archives: a streaming strategy +which is fast and can handle extremely large archives, and a +seeking strategy which can correctly process self-extracting +Zip archives and archives with deleted members or other +in-place modifications.</p> <p style="margin-left:6%; margin-top: 1em">The streaming reader processes Zip archives as they are read. It can read @@ -468,9 +464,8 @@ Libarchive can read and write 7-Zip format archives. TODO: Need more information</p> <p style="margin-left:6%; margin-top: 1em"><b>CAB</b> <br> -Libarchive can read Microsoft Cabinet ( -’’CAB’’) format archives. TODO: Need -more information.</p> +Libarchive can read Microsoft Cabinet ( “CAB”) +format archives. TODO: Need more information.</p> <p style="margin-left:6%; margin-top: 1em"><b>LHA</b> <br> TODO: Information about libarchive’s LHA support</p> @@ -484,8 +479,8 @@ the RARv3 format. Libarchive can also read self-extracting RAR archives.</p> <p style="margin-left:6%; margin-top: 1em"><b>Warc</b> <br> -Libarchive can read and write ’’web -archives’’. TODO: Need more information</p> +Libarchive can read and write “web archives”. +TODO: Need more information</p> <p style="margin-left:6%; margin-top: 1em"><b>XAR</b> <br> Libarchive can read and write the XAR format used by many diff --git a/archivers/libarchive/files/doc/html/libarchive.3.html b/archivers/libarchive/files/doc/html/libarchive.3.html index 54e09ee3d6c..8e5b5ff11d5 100644 --- a/archivers/libarchive/files/doc/html/libarchive.3.html +++ b/archivers/libarchive/files/doc/html/libarchive.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:10 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:18 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -53,12 +53,12 @@ for:</p> <p><b>•</b></p> <p style="margin-left:12%;">most variants of the POSIX -’’ustar’’ format,</p> +“ustar” format,</p> <p><b>•</b></p> -<p style="margin-left:12%;">the POSIX ’’pax -interchange’’ format,</p> +<p style="margin-left:12%;">the POSIX “pax +interchange” format,</p> <p><b>•</b></p> @@ -117,12 +117,12 @@ format to use. The library can write</p> <p><b>•</b></p> <p style="margin-left:12%;">POSIX-standard -’’ustar’’ archives,</p> +“ustar” archives,</p> <p><b>•</b></p> -<p style="margin-left:12%;">POSIX ’’pax -interchange format’’ archives,</p> +<p style="margin-left:12%;">POSIX “pax interchange +format” archives,</p> <p><b>•</b></p> diff --git a/archivers/libarchive/files/doc/html/libarchive_changes.3.html b/archivers/libarchive/files/doc/html/libarchive_changes.3.html index 2a3dde77a64..b686e68a0f2 100644 --- a/archivers/libarchive/files/doc/html/libarchive_changes.3.html +++ b/archivers/libarchive/files/doc/html/libarchive_changes.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:10 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:18 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -57,13 +57,13 @@ can be easily converted to UTF-8.</p> <p style="margin-left:6%; margin-top: 1em">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:</p> +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:</p> <p style="margin-left:6%; margin-top: 1em">If the archive_entry object is bound to an archive, it will use the diff --git a/archivers/libarchive/files/doc/html/libarchive_internals.3.html b/archivers/libarchive/files/doc/html/libarchive_internals.3.html index cf757b58c74..5a97aa0ab29 100644 --- a/archivers/libarchive/files/doc/html/libarchive_internals.3.html +++ b/archivers/libarchive/files/doc/html/libarchive_internals.3.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:10 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:18 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/mtree.5.html b/archivers/libarchive/files/doc/html/mtree.5.html index a276365abd6..813e4a26759 100644 --- a/archivers/libarchive/files/doc/html/mtree.5.html +++ b/archivers/libarchive/files/doc/html/mtree.5.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:10 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:19 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -175,8 +175,8 @@ pathname of a file that holds the contents of this file.</p> <p style="margin-left:22%; margin-top: 1em">The file flags as a symbolic name. See chflags(1) for information on these names. If no flags are to be set the string -’’none’’ may be used to override the -current default.</p> +“none” may be used to override the current +default.</p> <p style="margin-top: 1em"><b>gid</b></p> @@ -239,9 +239,9 @@ file hierarchy.</p> <p style="margin-top: 1em"><b>resdevice</b></p> <p style="margin-left:22%; margin-top: 1em">The -’’resident’’ device number of the -file, e.g. the ID of the device that contains the file. Its -format is the same as the one for <b>device</b>.</p> +“resident” device number of the file, e.g. the +ID of the device that contains the file. Its format is the +same as the one for <b>device</b>.</p> <p style="margin-top: 1em"><b>ripemd160digest</b></p> @@ -261,8 +261,7 @@ the file.</p> <p style="margin-top: 1em"><b>sha1</b></p> <p style="margin-left:22%; margin-top: 1em">The FIPS 160-1 -(’’SHA-1’’) message digest of the -file.</p> +(“SHA-1”) message digest of the file.</p> <p style="margin-top: 1em"><b>sha1digest</b></p> @@ -272,8 +271,7 @@ file.</p> <p style="margin-top: 1em"><b>sha256</b></p> <p style="margin-left:22%; margin-top: 1em">The FIPS 180-2 -(’’SHA-256’’) message digest of the -file.</p> +(“SHA-256”) message digest of the file.</p> <p style="margin-top: 1em"><b>sha256digest</b></p> @@ -283,8 +281,7 @@ file.</p> <p style="margin-top: 1em"><b>sha384</b></p> <p style="margin-left:22%; margin-top: 1em">The FIPS 180-2 -(’’SHA-384’’) message digest of the -file.</p> +(“SHA-384”) message digest of the file.</p> <p style="margin-top: 1em"><b>sha384digest</b></p> @@ -294,8 +291,7 @@ file.</p> <p style="margin-top: 1em"><b>sha512</b></p> <p style="margin-left:22%; margin-top: 1em">The FIPS 180-2 -(’’SHA-512’’) message digest of the -file.</p> +(“SHA-512”) message digest of the file.</p> <p style="margin-top: 1em"><b>sha512digest</b></p> @@ -374,8 +370,7 @@ digests were added in FreeBSD 4.0, as new attacks have demonstrated weaknesses in MD5. The SHA-256 digest was added in FreeBSD 6.0. Support for file flags was added in FreeBSD 4.0, and mostly comes from NetBSD. The -’’full’’ entry format was added by -NetBSD.</p> +“full” entry format was added by NetBSD.</p> <p style="margin-left:6%; margin-top: 1em">BSD September 4, 2013 BSD</p> diff --git a/archivers/libarchive/files/doc/html/tar.5.html b/archivers/libarchive/files/doc/html/tar.5.html index c9af4d8acf9..a718b1d2f7e 100644 --- a/archivers/libarchive/files/doc/html/tar.5.html +++ b/archivers/libarchive/files/doc/html/tar.5.html @@ -1,5 +1,5 @@ -<!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Mon Sep 3 22:55:10 2018 --> +<!-- Creator : groff version 1.22.4 --> +<!-- CreationDate: Wed Jun 12 21:10:19 2019 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -50,16 +50,15 @@ entirely of zero bytes.</p> compatibility with tape drives that use fixed block sizes, programs that read or write tar files always read or write a fixed number of records with each I/O operation. These -’’blocks’’ are always a multiple of -the record size. The maximum block size supported by early +“blocks” are always a multiple of the record +size. The maximum block size supported by early implementations was 10240 bytes or 20 records. This is still the default for most implementations although block sizes of 1MiB (2048 records) or larger are commonly used with modern -high-speed tape drives. (Note: the terms -’’block’’ and -’’record’’ here are not entirely -standard; this document follows the convention established -by John Gilmore in documenting <b>pdtar</b>.)</p> +high-speed tape drives. (Note: the terms “block” +and “record” here are not entirely standard; +this document follows the convention established by John +Gilmore in documenting <b>pdtar</b>.)</p> <p style="margin-left:6%; margin-top: 1em"><b>Old-Style Archive Format</b> <br> @@ -239,25 +238,25 @@ size and mtime fields must end in a space; the checksum is terminated by a null and a space. Early implementations filled the numeric fields with leading spaces. This seems to have been common practice until the IEEE Std 1003.1-1988 -(’’POSIX.1’’) standard was released. -For best portability, modern implementations should fill the -numeric fields with leading zeros.</p> +(“POSIX.1”) standard was released. For best +portability, modern implementations should fill the numeric +fields with leading zeros.</p> <p style="margin-left:6%; margin-top: 1em"><b>Pre-POSIX Archives</b> <br> An early draft of IEEE Std 1003.1-1988 -(’’POSIX.1’’) served as the basis -for John Gilmore’s <b>pdtar</b> program and many -system implementations from the late 1980s and early 1990s. -These archives generally follow the POSIX ustar format -described below with the following variations:</p> +(“POSIX.1”) served as the basis for John +Gilmore’s <b>pdtar</b> program and many system +implementations from the late 1980s and early 1990s. These +archives generally follow the POSIX ustar format described +below with the following variations:</p> <p><b>•</b></p> <p style="margin-left:17%;">The magic value consists of the -five characters ’’ustar’’ followed -by a space. The version field contains a space character -followed by a null.</p> +five characters “ustar” followed by a space. The +version field contains a space character followed by a +null.</p> <p><b>•</b></p> @@ -273,13 +272,13 @@ archives.</p> <p style="margin-left:6%; margin-top: 1em"><b>POSIX ustar Archives</b> <br> -IEEE Std 1003.1-1988 (’’POSIX.1’’) -defined a standard tar file format to be read and written by -compliant implementations of tar(1). This format is often -called the ’’ustar’’ format, after -the magic value used in the header. (The name is an acronym -for ’’Unix Standard TAR’’.) It -extends the historic format with new fields:</p> +IEEE Std 1003.1-1988 (“POSIX.1”) defined a +standard tar file format to be read and written by compliant +implementations of tar(1). This format is often called the +“ustar” format, after the magic value used in +the header. (The name is an acronym for “Unix Standard +TAR”.) It extends the historic format with new +fields:</p> <p style="margin-left:14%; margin-top: 1em">struct header_posix_ustar {</p> @@ -432,40 +431,40 @@ header_posix_ustar {</p> the earlier <i>linkflag</i> field with several new type values:</p> -<p>’’0’’</p> +<p>“0”</p> <p style="margin-left:27%; margin-top: 1em">Regular file. NUL should be treated as a synonym, for compatibility purposes.</p> -<p>’’1’’</p> +<p>“1”</p> <p style="margin-left:27%; margin-top: 1em">Hard link.</p> -<p>’’2’’</p> +<p>“2”</p> <p style="margin-left:27%; margin-top: 1em">Symbolic link.</p> -<p>’’3’’</p> +<p>“3”</p> <p style="margin-left:27%; margin-top: 1em">Character device node.</p> -<p>’’4’’</p> +<p>“4”</p> <p style="margin-left:27%; margin-top: 1em">Block device node.</p> -<p>’’5’’</p> +<p>“5”</p> <p style="margin-left:27%; margin-top: 1em">Directory.</p> -<p>’’6’’</p> +<p>“6”</p> <p style="margin-left:27%; margin-top: 1em">FIFO node.</p> -<p>’’7’’</p> +<p>“7”</p> <p style="margin-left:27%; margin-top: 1em">Reserved.</p> @@ -493,16 +492,16 @@ should be set to zero by writers and ignored by readers.</p> <p style="margin-top: 1em"><i>magic</i></p> <p style="margin-left:17%; margin-top: 1em">Contains the -magic value ’’ustar’’ followed by a -NUL byte to indicate that this is a POSIX standard archive. -Full compliance requires the uname and gname fields be -properly set.</p> +magic value “ustar” followed by a NUL byte to +indicate that this is a POSIX standard archive. Full +compliance requires the uname and gname fields be properly +set.</p> <p style="margin-top: 1em"><i>version</i></p> <p style="margin-left:17%;">Version. This should be -’’00’’ (two copies of the ASCII -digit zero) for POSIX standard archives.</p> +“00” (two copies of the ASCII digit zero) for +POSIX standard archives.</p> <p style="margin-top: 1em"><i>uname</i>, <i>gname</i></p> @@ -589,17 +588,16 @@ implementation.</p> Interchange Format</b> <br> There are many attributes that cannot be portably stored in a POSIX ustar archive. IEEE Std 1003.1-2001 -(’’POSIX.1’’) defined a -’’pax interchange format’’ that uses -two new types of entries to hold text-formatted metadata -that applies to following entries. Note that a pax -interchange format archive is a ustar archive in every -respect. The new data is stored in ustar-compatible archive -entries that use the ’’x’’ or -’’g’’ typeflag. In particular, older -implementations that do not fully support these extensions -will extract the metadata into regular files, where the -metadata can be examined as necessary.</p> +(“POSIX.1”) defined a “pax interchange +format” that uses two new types of entries to hold +text-formatted metadata that applies to following entries. +Note that a pax interchange format archive is a ustar +archive in every respect. The new data is stored in +ustar-compatible archive entries that use the +“x” or “g” typeflag. In particular, +older implementations that do not fully support these +extensions will extract the metadata into regular files, +where the metadata can be examined as necessary.</p> <p style="margin-left:6%; margin-top: 1em">An entry in a pax interchange format archive consists of one or two @@ -640,17 +638,16 @@ pax extended attributes are assumed to be in UTF-8, including pathnames, user names, and group names. In some cases, it is not possible to translate local conventions into UTF-8. If this key is present and the value is the -six-character ASCII string -’’BINARY’’, then all textual values -are assumed to be in a platform-dependent multi-byte -encoding. Note that there are only two valid values for this -key: ’’BINARY’’ or -’’ISO-IR 10646 2000 UTF-8’’. -No other values are permitted by the standard, and the -latter value should generally not be used as it is the -default when this key is not specified. In particular, this -flag should not be used as a general mechanism to allow -filenames to be stored in arbitrary encodings.</p> +six-character ASCII string “BINARY”, then all +textual values are assumed to be in a platform-dependent +multi-byte encoding. Note that there are only two valid +values for this key: “BINARY” or +“ISO-IR 10646 2000 UTF-8”. No +other values are permitted by the standard, and the latter +value should generally not be used as it is the default when +this key is not specified. In particular, this flag should +not be used as a general mechanism to allow filenames to be +stored in arbitrary encodings.</p> <p style="margin-top: 1em"><b>uname</b>, <b>uid</b>, <b>gname</b>, <b>gid</b></p> @@ -739,8 +736,8 @@ it.</p> <p style="margin-left:17%;">The time when the file was created. (This should not be confused with the POSIX -’’ctime’’ attribute, which refers to -the time when the file metadata was last changed.)</p> +“ctime” attribute, which refers to the time when +the file metadata was last changed.)</p> <p style="margin-top: 1em"><b>LIBARCHIVE.xattr.</b><i>namespace</i>.<i>key</i></p> @@ -748,13 +745,11 @@ the time when the file metadata was last changed.)</p> <p style="margin-left:17%;">Libarchive stores POSIX.1e-style extended attributes using keys of this form. The <i>key</i> value is URL-encoded: All non-ASCII -characters and the two special characters -’’=’’ and -’’%’’ are encoded as -’’%’’ followed by two uppercase -hexadecimal digits. The value of this key is the extended -attribute value encoded in base 64. XXX Detail the base-64 -format here XXX</p> +characters and the two special characters “=” +and “%” are encoded as “%” followed +by two uppercase hexadecimal digits. The value of this key +is the extended attribute value encoded in base 64. XXX +Detail the base-64 format here XXX</p> <p style="margin-top: 1em"><b>VENDOR.*</b></p> @@ -1137,23 +1132,21 @@ equal to realsize.</p> They contained a list of files to be renamed or symlinked after extraction; this was originally used to support long names. The contents of this record are a text description of -the operations to be done, in the form ’’Rename -%s to %s\n’’ or ’’Symlink %s to -%s\n’’; in either case, both filenames are -escaped using K&R C syntax. Due to security concerns, -"N" records are now generally ignored when reading -archives.</p> +the operations to be done, in the form “Rename %s to +%s\n” or “Symlink %s to %s\n”; in either +case, both filenames are escaped using K&R C syntax. Due +to security concerns, "N" records are now +generally ignored when reading archives.</p> <p style="margin-top: 1em">S</p> <p style="margin-left:27%; margin-top: 1em">This is a -’’sparse’’ regular file. Sparse -files are stored as a series of fragments. The header -contains a list of fragment offset/length pairs. If more -than four such entries are required, the header is extended -as necessary with ’’extra’’ header -extensions (an older format that is no longer used), or -’’sparse’’ extensions.</p> +“sparse” regular file. Sparse files are stored +as a series of fragments. The header contains a list of +fragment offset/length pairs. If more than four such entries +are required, the header is extended as necessary with +“extra” header extensions (an older format that +is no longer used), or “sparse” extensions.</p> <p style="margin-top: 1em">V</p> @@ -1164,16 +1157,15 @@ This entry should generally be ignored on extraction.</p> <p style="margin-top: 1em"><i>magic</i></p> <p style="margin-left:17%; margin-top: 1em">The magic field -holds the five characters ’’ustar’’ -followed by a space. Note that POSIX ustar archives have a -trailing null.</p> +holds the five characters “ustar” followed by a +space. Note that POSIX ustar archives have a trailing +null.</p> <p style="margin-top: 1em"><i>version</i></p> <p style="margin-left:17%;">The version field holds a space character followed by a null. Note that POSIX ustar archives -use two copies of the ASCII digit -’’0’’.</p> +use two copies of the ASCII digit “0”.</p> <p style="margin-top: 1em"><i>atime</i>, <i>ctime</i></p> @@ -1200,10 +1192,10 @@ written to the file at appropriate offsets.</p> <p style="margin-top: 1em"><i>isextended</i></p> <p style="margin-left:17%;">If this is set to non-zero, the -header will be followed by additional ’’sparse -header’’ records. Each such record contains -information about as many as 21 additional sparse blocks as -shown here:</p> +header will be followed by additional “sparse +header” records. Each such record contains information +about as many as 21 additional sparse blocks as shown +here:</p> <p style="margin-left:24%; margin-top: 1em">struct gnu_sparse_header {</p> @@ -1288,52 +1280,49 @@ interchange format archives when you specify the format closely, using some <b>SCHILY</b> tags and introducing new keywords to store sparse file information. There have been three iterations of the sparse file support, -referred to as ’’0.0’’, -’’0.1’’, and -’’1.0’’.</p> +referred to as “0.0”, “0.1”, and +“1.0”.</p> <p style="margin-top: 1em"><b>GNU.sparse.numblocks</b>, <b>GNU.sparse.offset</b>, <b>GNU.sparse.numbytes</b>, <b>GNU.sparse.size</b></p> -<p style="margin-left:17%;">The -’’0.0’’ format used an initial -<b>GNU.sparse.numblocks</b> attribute to indicate the number -of blocks in the file, a pair of <b>GNU.sparse.offset</b> -and <b>GNU.sparse.numbytes</b> to indicate the offset and -size of each block, and a single <b>GNU.sparse.size</b> to -indicate the full size of the file. This is not the same as -the size in the tar header because the latter value does not -include the size of any holes. This format required that the -order of attributes be preserved and relied on readers -accepting multiple appearances of the same attribute names, -which is not officially permitted by the standards.</p> +<p style="margin-left:17%;">The “0.0” format +used an initial <b>GNU.sparse.numblocks</b> attribute to +indicate the number of blocks in the file, a pair of +<b>GNU.sparse.offset</b> and <b>GNU.sparse.numbytes</b> to +indicate the offset and size of each block, and a single +<b>GNU.sparse.size</b> to indicate the full size of the +file. This is not the same as the size in the tar header +because the latter value does not include the size of any +holes. This format required that the order of attributes be +preserved and relied on readers accepting multiple +appearances of the same attribute names, which is not +officially permitted by the standards.</p> <p style="margin-top: 1em"><b>GNU.sparse.map</b></p> -<p style="margin-left:17%;">The -’’0.1’’ format used a single -attribute that stored a comma-separated list of decimal -numbers. Each pair of numbers indicated the offset and size, -respectively, of a block of data. This does not work well if -the archive is extracted by an archiver that does not -recognize this extension, since many pax implementations -simply discard unrecognized attributes.</p> +<p style="margin-left:17%;">The “0.1” format +used a single attribute that stored a comma-separated list +of decimal numbers. Each pair of numbers indicated the +offset and size, respectively, of a block of data. This does +not work well if the archive is extracted by an archiver +that does not recognize this extension, since many pax +implementations simply discard unrecognized attributes.</p> <p style="margin-top: 1em"><b>GNU.sparse.major</b>, <b>GNU.sparse.minor</b>, <b>GNU.sparse.name</b>, <b>GNU.sparse.realsize</b></p> -<p style="margin-left:17%;">The -’’1.0’’ format stores the sparse -block map in one or more 512-byte blocks prepended to the -file data in the entry body. The pax attributes indicate the -existence of this map (via the <b>GNU.sparse.major</b> and -<b>GNU.sparse.minor</b> fields) and the full size of the -file. The <b>GNU.sparse.name</b> holds the true name of the -file. To avoid confusion, the name stored in the regular tar -header is a modified name so that extraction errors will be -apparent to users.</p> +<p style="margin-left:17%;">The “1.0” format +stores the sparse block map in one or more 512-byte blocks +prepended to the file data in the entry body. The pax +attributes indicate the existence of this map (via the +<b>GNU.sparse.major</b> and <b>GNU.sparse.minor</b> fields) +and the full size of the file. The <b>GNU.sparse.name</b> +holds the true name of the file. To avoid confusion, the +name stored in the regular tar header is a modified name so +that extraction errors will be apparent to users.</p> <p style="margin-left:6%; margin-top: 1em"><b>Solaris Tar</b> <br> @@ -1341,9 +1330,9 @@ XXX More Details Needed XXX</p> <p style="margin-left:6%; margin-top: 1em">Solaris tar (beginning with SunOS XXX 5.7 ?? XXX) supports an -’’extended’’ format that is -fundamentally similar to pax interchange format, with the -following differences:</p> +“extended” format that is fundamentally similar +to pax interchange format, with the following +differences:</p> <p><b>•</b></p> @@ -1380,17 +1369,17 @@ Tar</b> <br> The tar distributed with Apple’s Mac OS X stores most regular files as two separate files in the tar archive. The two files have the same name except that the first one has -’’._’’ prepended to the last path -element. This special file stores an AppleDouble-encoded -binary blob with additional metadata about the second file, -including ACL, extended attributes, and resources. To -recreate the original file on disk, each separate file can -be extracted and the Mac OS X <b>copyfile</b>() function can -be used to unpack the separate metadata file and apply it to -th regular file. Conversely, the same function provides a -’’pack’’ option to encode the -extended metadata from a file into a separate file whose -contents can then be put into a tar archive.</p> +“._” prepended to the last path element. This +special file stores an AppleDouble-encoded binary blob with +additional metadata about the second file, including ACL, +extended attributes, and resources. To recreate the original +file on disk, each separate file can be extracted and the +Mac OS X <b>copyfile</b>() function can be used to unpack +the separate metadata file and apply it to th regular file. +Conversely, the same function provides a “pack” +option to encode the extended metadata from a file into a +separate file whose contents can then be put into a tar +archive.</p> <p style="margin-left:6%; margin-top: 1em">Note that the Apple extended attributes interact badly with long @@ -1526,11 +1515,11 @@ interchange format per-file extensions.</p> <p style="margin-left:6%;">The <b>tar</b> utility is no longer a part of POSIX or the Single Unix Standard. It last appeared in Version 2 of the Single UNIX Specification -(’’SUSv2’’). It has been supplanted -in subsequent standards by pax(1). The ustar format is -currently part of the specification for the pax(1) utility. -The pax interchange file format is new with IEEE Std -1003.1-2001 (’’POSIX.1’’).</p> +(“SUSv2”). It has been supplanted in subsequent +standards by pax(1). The ustar format is currently part of +the specification for the pax(1) utility. The pax +interchange file format is new with IEEE Std 1003.1-2001 +(“POSIX.1”).</p> <p style="margin-top: 1em"><b>HISTORY</b></p> |