summaryrefslogtreecommitdiff
path: root/archivers/libarchive/files/doc/wiki/ManPageLibarchiveInternals3.wiki
diff options
context:
space:
mode:
Diffstat (limited to 'archivers/libarchive/files/doc/wiki/ManPageLibarchiveInternals3.wiki')
-rw-r--r--archivers/libarchive/files/doc/wiki/ManPageLibarchiveInternals3.wiki22
1 files changed, 11 insertions, 11 deletions
diff --git a/archivers/libarchive/files/doc/wiki/ManPageLibarchiveInternals3.wiki b/archivers/libarchive/files/doc/wiki/ManPageLibarchiveInternals3.wiki
index a980ba4ce33..c7841683462 100644
--- a/archivers/libarchive/files/doc/wiki/ManPageLibarchiveInternals3.wiki
+++ b/archivers/libarchive/files/doc/wiki/ManPageLibarchiveInternals3.wiki
@@ -13,15 +13,15 @@ make it easy to add new archive and compression formats.
Externally, libarchive exposes most operations through an
opaque, object-style interface.
The
-[[ManPagerchiventry3]]
+[[ManPageArchiveEntry3]]
objects store information about a single filesystem object.
The rest of the library provides facilities to write
-[[ManPagerchiventry3]]
+[[ManPageArchiveEntry3]]
objects to archive files,
read them from archive files,
and write them to disk.
(There are plans to add a facility to read
-[[ManPagerchiventry3]]
+[[ManPageArchiveEntry3]]
objects from disk as well.)
The read and write APIs each have four layers: a public API
@@ -37,7 +37,7 @@ an archive or disk writer, and then use a single set of
code to select and write entries, regardless of the target.
== READ ARCHITECTURE ==
From the outside, clients use the
-[[ManPagerchiveead3]]
+[[ManPageArchiveRead3]]
API to manipulate an
'''archive'''
object to read entries and bodies from an archive stream.
@@ -50,9 +50,9 @@ The API has four layers:
The lowest layer is the I/O layer.
This layer can be overridden by clients, but most clients use
the packaged I/O callbacks provided, for example, by
-[[ManPagerchiveeadpenemory3]],
+[[ManPageArchiveReadOpenMemory3]],
and
-[[ManPagerchiveeadpend3]].
+[[ManPageArchiveReadOpenFd3]].
The compression layer calls the I/O layer to
read bytes and decompresses them for the format layer.
The format layer unpacks a stream of uncompressed bytes and
@@ -319,11 +319,11 @@ Fortunately, such archives are very rare, and libarchive can read
most ZIP archives, though it cannot always extract as much information
as a dedicated ZIP program.
== SEE ALSO ==
-[[ManPagerchiventry3]],
-[[ManPagerchiveead3]],
-[[ManPagerchiverite3]],
-[[ManPagerchiveriteisk3]]
-[[ManPageibarchive3]],
+[[ManPageArchiveEntry3]],
+[[ManPageArchiveRead3]],
+[[ManPageArchiveWrite3]],
+[[ManPageArchiveWriteDisk3]]
+[[ManPageLibarchive3]],
== HISTORY ==
The
'''libarchive'''