This patch is needed to convert BSD-style section numbers to Solaris-style
section numbers. It has not been fed back to the upstream community. It
may need to be tweaked slightly for future releases.
--- libarchive/libarchive/archive_write_disk.3.orig Mon Mar 26 19:49:00 2012
+++ libarchive/libarchive/archive_write_disk.3 Fri Nov 9 12:33:36 2012
@@ -25,7 +25,7 @@
.\" $FreeBSD$
.\"
.Dd February 2, 2012
-.Dt ARCHIVE_WRITE_DISK 3
+.Dt ARCHIVE_WRITE_DISK 3ARCHIVE
.Os
.Sh NAME
.Nm archive_write_disk_new ,
@@ -207,22 +207,22 @@
This convenience function installs a standard set of user
and group lookup functions.
These functions use
-.Xr getpwnam 3
+.Xr getpwnam 3C
and
-.Xr getgrnam 3
+.Xr getgrnam 3C
to convert names to ids, defaulting to the ids if the names cannot
be looked up.
These functions also implement a simple memory cache to reduce
the number of calls to
-.Xr getpwnam 3
+.Xr getpwnam 3C
and
-.Xr getgrnam 3 .
+.Xr getgrnam 3C .
.It Fn archive_write_header
Build and write a header using the data in the provided
.Tn struct archive_entry
structure.
See
-.Xr archive_entry 3
+.Xr archive_entry 3ARCHIVE
for information on creating and populating
.Tn struct archive_entry
objects.
@@ -275,10 +275,10 @@
More information about the
.Va struct archive
object and the overall design of the library can be found in the
-.Xr libarchive 3
+.Xr libarchive 3LIB
overview.
Many of these functions are also documented under
-.Xr archive_write 3 .
+.Xr archive_write 3ARCHIVE .
.Sh RETURN VALUES
Most functions return
.Cm ARCHIVE_OK
@@ -311,10 +311,10 @@
functions.
.\"
.Sh SEE ALSO
-.Xr archive_read 3 ,
-.Xr archive_write 3 ,
+.Xr archive_read 3ARCHIVE ,
+.Xr archive_write 3ARCHIVE ,
.Xr tar 1 ,
-.Xr libarchive 3
+.Xr libarchive 3LIB
.Sh HISTORY
The
.Nm libarchive
@@ -390,9 +390,9 @@
The
.Dq standard
user-id and group-id lookup functions are not the defaults because
-.Xr getgrnam 3
+.Xr getgrnam 3C
and
-.Xr getpwnam 3
+.Xr getpwnam 3C
are sometimes too large for particular applications.
The current design allows the application author to use a more
compact implementation when appropriate.