Merge conflicts from 3.4.0 to 3.7.4

Introduce ARCHIVE_EXTRACT_ATOMIC and set it by default on bsdtar.

This flag changes the way that regular files are extracted:

Instead of removing existing files first and re-creating them in
order to replace their contents, a temporary file is created and
when writing to the temporary file is completed, the file is
rename(2)d to the final destination name.

This has the effect of presenting a consistent view of the file to
the system (either the file with the new contents or the file with
the old contents). Removing and overwriting the file has the
undesired side effect that the the system can either not see the
file at all (from the time it is being removed till the time it is
being re-created), or worse it can see partial file contents. This
is problematic when extracting system files (for example shared
libraries).

Perhaps there should be a flag to disable it, when for example it
is not desirable because of space constraints, but then again
one can specify to unlink the file before.

(this is pull request 1289)

branches: 1.1.1;
Initial revision

Introduce ARCHIVE_EXTRACT_ATOMIC and set it by default on bsdtar.

This flag changes the way that regular files are extracted:

Instead of removing existing files first and re-creating them in
order to replace their contents, a temporary file is created and
when writing to the temporary file is completed, the file is
rename(2)d to the final destination name.

This has the effect of presenting a consistent view of the file to
the system (either the file with the new contents or the file with
the old contents). Removing and overwriting the file has the
undesired side effect that the the system can either not see the
file at all (from the time it is being removed till the time it is
being re-created), or worse it can see partial file contents. This
is problematic when extracting system files (for example shared
libraries).

Perhaps there should be a flag to disable it, when for example it
is not desirable because of space constraints, but then again
one can specify to unlink the file before.

(this is pull request 1289)

branches: 1.1.1;
Initial revision

Import libarchive 3.3.2pre (7ad477ea7655f3dfcdcfa5adcb792f0ec864969d).

branches: 1.1.1.2.30; 1.1.1.2.34;
Import libarchive 2.8.0:
- Infrastructure:
- Allow command line tools as fallback for missing compression
libraries. If compiled without gzip for example, gunzip will
be used automatically.
- Improved support for a number of platforms like high-resolution
timestamps and Extended Attributes on various Unix systems
- New convience interface for creating archives based on disk content,
complement of the archive_write_disk interface.
- Frontends:
- bsdcpio ready for public consumption
- hand-written date parser replaces the yacc code
- Filter system:
- Simplified read filter chains
- Option support for filters
- LZMA, XZ, uudecode handled
- Format support:
- Write support for mtree files based on file system or archive
content
- Basic read support for Joliet
- Write support for zip files
- Write support for shar archives, both text-only and binary-safe

branches: 1.1.1.1.4; 1.1.1.1.12; 1.1.1.1.14;
Import libarchive-2.5.5. This makes bsdcpio more compatible with GNU
cpio's long options, copyies links when they cross devices in copy mode.
A number of other smaller bugfixes and improvements were added.

branches: 1.1.1;
Initial revision

Import libarchive 2.8.0:
- Infrastructure:
- Allow command line tools as fallback for missing compression
libraries. If compiled without gzip for example, gunzip will
be used automatically.
- Improved support for a number of platforms like high-resolution
timestamps and Extended Attributes on various Unix systems
- New convience interface for creating archives based on disk content,
complement of the archive_write_disk interface.
- Frontends:
- bsdcpio ready for public consumption
- hand-written date parser replaces the yacc code
- Filter system:
- Simplified read filter chains
- Option support for filters
- LZMA, XZ, uudecode handled
- Format support:
- Write support for mtree files based on file system or archive
content
- Basic read support for Joliet
- Write support for zip files
- Write support for shar archives, both text-only and binary-safe

branches: 1.1.1.1.4; 1.1.1.1.12; 1.1.1.1.14;
Import libarchive-2.5.5. This makes bsdcpio more compatible with GNU
cpio's long options, copyies links when they cross devices in copy mode.
A number of other smaller bugfixes and improvements were added.

Pull up pkg_install-20090528, libarchive-2.5.5 and libfetch-2.23
with the associated build infrastructure as of 20090929 from HEAD.

file archive_private.h was added on branch netbsd-4 on 2009-06-05 17:19:31 +0000

Apply patch (requested by joerg in ticket #1322):
Pull up pkg_install-20090528, libarchive-2.5.5 and libfetch-2.23
with the associated build infrastructure as of 20090529 from HEAD.

file archive_private.h was added on branch netbsd-4-0 on 2009-06-05 17:01:49 +0000

Sync with HEAD.

file archive_private.h was added on branch haad-dm on 2008-10-19 22:39:52 +0000