cmclark00/retro-imager
1
0
Fork 0
mirror of https://github.com/cmclark00/retro-imager.git synced 2025-05-19 16:35:20 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Qt/QML edition

Browse source
This commit is contained in:
Floris Bos 2020-03-04 16:55:40 +01:00
commit d7b361ba44
2168 changed files with 721948 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

212
dependencies/libarchive-3.4.2/doc/html/archive_entry_linkify.3.html vendored Normal file
View file

@ -0,0 +1,212 @@
<!-- Creator : groff version 1.22.3 -->
<!-- CreationDate: Tue Feb 11 22:58:43 2020 -->
<!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_LINKIFY(3) BSD Library Functions Manual
ARCHIVE_ENTRY_LINKIFY(3)</p>
<p style="margin-top: 1em"><b>NAME</b></p>
<p style="margin-left:6%;"><b>archive_entry_linkresolver</b>,
<b>archive_entry_linkresolver_new</b>,
<b>archive_entry_linkresolver_set_strategy</b>,
<b>archive_entry_linkresolver_free</b>,
<b>archive_entry_linkify</b> &mdash; hardlink resolver
functions</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
&lt;archive_entry.h&gt;</b></p>
<p style="margin-left:6%; margin-top: 1em"><i>struct
archive_entry_linkresolver *</i></p>
<p style="margin-left:12%;"><b>archive_entry_linkresolver_new</b>(<i>void</i>);</p>
<p style="margin-left:6%; margin-top: 1em"><i>void</i></p>
<p><b>archive_entry_linkresolver_set_strategy</b>(<i>struct&nbsp;archive_entry_linkresolver&nbsp;*resolver</i>,
<i>int&nbsp;format</i>);</p>
<p style="margin-left:6%; margin-top: 1em"><i>void</i></p>
<p><b>archive_entry_linkresolver_free</b>(<i>struct&nbsp;archive_entry_linkresolver&nbsp;*resolver</i>);</p>
<p style="margin-left:6%; margin-top: 1em"><i>void</i></p>
<p><b>archive_entry_linkify</b>(<i>struct&nbsp;archive_entry_linkresolver&nbsp;*resolver</i>,
<i>struct&nbsp;archive_entry&nbsp;**entry</i>,
<i>struct&nbsp;archive_entry&nbsp;**sparse</i>);</p>
<p style="margin-top: 1em"><b>DESCRIPTION</b></p>
<p style="margin-left:6%;">Programs that want to create
archives have to deal with hardlinks. Hardlinks are handled
in different ways by the archive formats. The basic
strategies are:</p>
<p style="margin-top: 1em">1.</p>
<p style="margin-left:13%;">Ignore hardlinks and store the
body for each reference (old cpio, zip).</p>
<p style="margin-top: 1em">2.</p>
<p style="margin-left:13%;">Store the body the first time
an inode is seen (ustar, pax).</p>
<p style="margin-top: 1em">3.</p>
<p style="margin-left:13%;">Store the body the last time an
inode is seen (new cpio).</p>
<p style="margin-left:6%; margin-top: 1em">The
<b>archive_entry_linkresolver</b> functions help by
providing a unified interface and handling the complexity
behind the scene.</p>
<p style="margin-left:6%; margin-top: 1em">The
<b>archive_entry_linkresolver</b> functions assume that
<i>archive_entry</i> instances have valid nlinks, inode and
device values. The inode and device value is used to match
entries. The nlinks value is used to determined if all
references have been found and if the internal references
can be recycled.</p>
<p style="margin-left:6%; margin-top: 1em">The
<b>archive_entry_linkresolver_new</b>() function allocates a
new link resolver. The instance can be freed using
<b>archive_entry_linkresolver_free</b>(). All deferred
entries are flushed and the internal storage is freed.</p>
<p style="margin-left:6%; margin-top: 1em">The
<b>archive_entry_linkresolver_set_strategy</b>() function
selects the optimal hardlink strategy for the given format.
The format code can be obtained from archive_format(3). The
function can be called more than once, but it is recommended
to flush all deferred entries first.</p>
<p style="margin-left:6%; margin-top: 1em">The
<b>archive_entry_linkify</b>() function is the core of
<b>archive_entry_linkresolver</b>. The <b>entry</b>()
argument points to the <i>archive_entry</i> that should be
written. Depending on the strategy one of the following
actions is taken:</p>
<p style="margin-top: 1em">1.</p>
<p style="margin-left:13%;">For the simple archive formats
<i>*entry</i> is left unmodified and <i>*sparse</i> is set
to NULL.</p>
<p style="margin-top: 1em">2.</p>
<p style="margin-left:13%;">For tar like archive formats,
<i>*sparse</i> is set to NULL. If <i>*entry</i> is NULL, no
action is taken. If the hardlink count of <i>*entry</i> is
larger than 1 and the file type is a regular file or
symbolic link, the internal list is searched for a matching
inode. If such an inode is found, the link count is
decremented and the file size of <i>*entry</i> is set to 0
to notify that no body should be written. If no such inode
is found, a copy of the entry is added to the internal cache
with a link count reduced by one.</p>
<p style="margin-top: 1em">3.</p>
<p style="margin-left:13%;">For new cpio like archive
formats a value for <i>*entry</i> of NULL is used to flush
deferred entries. In that case <i>*entry</i> is set to an
arbitrary deferred entry and the entry itself is removed
from the internal list. If the internal list is empty,
<i>*entry</i> is set to NULL. In either case, <i>*sparse</i>
is set to NULL and the function returns. If the hardlink
count of <i>*entry</i> is one or the file type is a
directory or device, <i>*sparse</i> is set to NULL and no
further action is taken. Otherwise, the internal list is
searched for a matching inode. If such an inode is not
found, the entry is added to the internal list, both
<i>*entry</i> and <i>*sparse</i> are set to NULL and the
function returns. If such an inode is found, the link count
is decremented. If it remains larger than one, the existing
entry on the internal list is swapped with <i>*entry</i>
after retaining the link count. The existing entry is
returned in <i>*entry</i>. If the link count reached one,
the new entry is also removed from the internal list and
returned in <i>*sparse</i>. Otherwise <i>*sparse</i> is set
to NULL.</p>
<p style="margin-left:6%; margin-top: 1em">The general
usage is therefore:</p>
<p style="margin-top: 1em">1.</p>
<p style="margin-left:13%;">For each new archive entry,
call <b>archive_entry_linkify</b>().</p>
<p style="margin-top: 1em">2.</p>
<p style="margin-left:13%;">Keep in mind that the entries
returned may have a size of 0 now.</p>
<p style="margin-top: 1em">3.</p>
<p style="margin-left:13%;">If <i>*entry</i> is not NULL,
archive it.</p>
<p style="margin-top: 1em">4.</p>
<p style="margin-left:13%;">If <i>*sparse</i> is not NULL,
archive it.</p>
<p style="margin-top: 1em">5.</p>
<p style="margin-left:13%;">After all entries have been
written to disk, call <b>archive_entry_linkify</b>() with
<i>*entry</i> set to NULL and archive the returned entry as
long as it is not NULL.</p>
<p style="margin-top: 1em"><b>RETURN VALUES</b></p>
<p style="margin-left:6%;"><b>archive_entry_linkresolver_new</b>()
returns NULL on malloc(3) failures.</p>
<p style="margin-top: 1em"><b>SEE ALSO</b></p>
<p style="margin-left:6%;">archive_entry(3)</p>
<p style="margin-left:6%; margin-top: 1em">BSD
February&nbsp;2, 2012 BSD</p>
<hr>
</body>
</html>