| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
modes of extracted files. This effectively disables special threating
of uid 0 for mode-preserving purposes and should fix problems with
pkg_add(1) and probably other things when extracting files/dirs with
sticky mode bits set.
Pointed out by: bde
MFC in: 2 weeks
|
| |
|
|
|
|
|
|
|
| |
in the archive, but its absence in the file system should be reported
as difference, not as error.
Reported by: bde
|
|
|
|
|
|
|
| |
already exists don't spew bogus "Cannot unlink" error and exit with
non-zero code.
Reported by: bde
|
|
|
|
|
|
| |
like "Cannot stat: (null)"
Reported by: bde, kris
|
|
|
|
|
|
|
| |
the --same-permissions was an overkill, so put it back. This is consistent
with what our old tar did.
Suggested by: dillon
|
|
|
|
|
|
|
| |
safely ignore current umask(2) and assume that permissions should be set
right like in the archive. Not only it violates POLA, but introduces
huge potential security vulnerability, particularly for ports, where
many popular archives come with 777 files and dirs.
|
|
|
|
|
| |
Requested by: ps
Reviewed by: md5(1)
|
| |
|
| |
|
|
|