package tar

Import Path
	archive/tar (on go.dev)

Dependency Relation
	imports 18 packages, and imported by 0 packages

Involved Source Files Package tar implements access to tar archives. Tape archives (tar) are a file format for storing a sequence of files that can be read and written in a streaming manner. This package aims to cover most variations of the format, including those produced by GNU and BSD tar tools. format.go reader.go stat_actime1.go stat_unix.go strconv.go writer.go
Code Examples package main import ( "archive/tar" "bytes" "fmt" "io" "log" "os" ) func main() { // Create and add some files to the archive. var buf bytes.Buffer tw := tar.NewWriter(&buf) var files = []struct { Name, Body string }{ {"readme.txt", "This archive contains some text files."}, {"gopher.txt", "Gopher names:\nGeorge\nGeoffrey\nGonzo"}, {"todo.txt", "Get animal handling license."}, } for _, file := range files { hdr := &tar.Header{ Name: file.Name, Mode: 0600, Size: int64(len(file.Body)), } if err := tw.WriteHeader(hdr); err != nil { log.Fatal(err) } if _, err := tw.Write([]byte(file.Body)); err != nil { log.Fatal(err) } } if err := tw.Close(); err != nil { log.Fatal(err) } // Open and iterate through the files in the archive. tr := tar.NewReader(&buf) for { hdr, err := tr.Next() if err == io.EOF { break // End of archive } if err != nil { log.Fatal(err) } fmt.Printf("Contents of %s:\n", hdr.Name) if _, err := io.Copy(os.Stdout, tr); err != nil { log.Fatal(err) } fmt.Println() } }
Package-Level Type Names (total 5)
/* sort by: | */
FileInfoNames extends [fs.FileInfo]. Passing an instance of this to [FileInfoHeader] permits the caller to avoid a system-dependent name lookup by specifying the Uname and Gname directly. Gname should give a group name. // abbreviation for Mode().IsDir() // modification time // file mode bits // base name of the file // length in bytes for regular files; system-dependent for others // underlying data source (can return nil) Uname should give a user name. FileInfoNames : io/fs.FileInfo
Format represents the tar archive format. The original tar format was introduced in Unix V7. Since then, there have been multiple competing formats attempting to standardize or extend the V7 format to overcome its limitations. The most common formats are the USTAR, PAX, and GNU formats, each with their own advantages and limitations. The following table captures the capabilities of each format: | USTAR | PAX | GNU ------------------+--------+-----------+---------- Name | 256B | unlimited | unlimited Linkname | 100B | unlimited | unlimited Size | uint33 | unlimited | uint89 Mode | uint21 | uint21 | uint57 Uid/Gid | uint21 | unlimited | uint57 Uname/Gname | 32B | unlimited | 32B ModTime | uint33 | unlimited | int89 AccessTime | n/a | unlimited | int89 ChangeTime | n/a | unlimited | int89 Devmajor/Devminor | uint21 | uint21 | uint57 ------------------+--------+-----------+---------- string encoding | ASCII | UTF-8 | binary sub-second times | no | yes | no sparse files | no | yes | yes The table's upper portion shows the [Header] fields, where each format reports the maximum number of bytes allowed for each string field and the integer type used to store each numeric field (where timestamps are stored as the number of seconds since the Unix epoch). The table's lower portion shows specialized features of each format, such as supported string encodings, support for sub-second timestamps, or support for sparse files. The Writer currently provides no support for sparse files. ( Format) String() string Format : expvar.Var Format : fmt.Stringer const FormatGNU const FormatPAX const FormatUnknown const FormatUSTAR
A Header represents a single header in a tar archive. Some fields may not be populated. For forward compatibility, users that retrieve a Header from Reader.Next, mutate it in some ways, and then pass it back to Writer.WriteHeader should do so by creating a new Header and copying the fields that they are interested in preserving. // Access time (requires either PAX or GNU support) // Change time (requires either PAX or GNU support) // Major device number (valid for TypeChar or TypeBlock) // Minor device number (valid for TypeChar or TypeBlock) Format specifies the format of the tar header. This is set by Reader.Next as a best-effort guess at the format. Since the Reader liberally reads some non-compliant files, it is possible for this to be FormatUnknown. If the format is unspecified when Writer.WriteHeader is called, then it uses the first format (in the order of USTAR, PAX, GNU) capable of encoding this Header (see Format). // Group ID of owner // Group name of owner // Target name of link (valid for TypeLink or TypeSymlink) If the Format is unspecified, then Writer.WriteHeader rounds ModTime to the nearest second and ignores the AccessTime and ChangeTime fields. To use AccessTime or ChangeTime, specify the Format as PAX or GNU. To use sub-second resolution, specify the Format as PAX. // Modification time // Permission and mode bits // Name of file entry PAXRecords is a map of PAX extended header records. User-defined records should have keys of the following form: VENDOR.keyword Where VENDOR is some namespace in all uppercase, and keyword may not contain the '=' character (e.g., "GOLANG.pkg.version"). The key and value should be non-empty UTF-8 strings. When Writer.WriteHeader is called, PAX records derived from the other fields in Header take precedence over PAXRecords. // Logical file size in bytes Typeflag is the type of header entry. The zero value is automatically promoted to either TypeReg or TypeDir depending on the presence of a trailing slash in Name. // User ID of owner // User name of owner Xattrs stores extended attributes as PAX records under the "SCHILY.xattr." namespace. The following are semantically equivalent: h.Xattrs[key] = value h.PAXRecords["SCHILY.xattr."+key] = value When Writer.WriteHeader is called, the contents of Xattrs will take precedence over those in PAXRecords. Deprecated: Use PAXRecords instead. FileInfo returns an fs.FileInfo for the Header. func FileInfoHeader(fi fs.FileInfo, link string) (*Header, error) func (*Reader).Next() (*Header, error) func (*Writer).WriteHeader(hdr *Header) error
Reader provides sequential access to the contents of a tar archive. Reader.Next advances to the next file in the archive (including the first), and then Reader can be treated as an io.Reader to access the file's data. Next advances to the next entry in the tar archive. The Header.Size determines how many bytes can be read for the next file. Any remaining data in the current file is automatically discarded. At the end of the archive, Next returns the error io.EOF. If Next encounters a non-local name (as defined by [filepath.IsLocal]) and the GODEBUG environment variable contains `tarinsecurepath=0`, Next returns the header with an [ErrInsecurePath] error. A future version of Go may introduce this behavior by default. Programs that want to accept non-local names can ignore the [ErrInsecurePath] error and use the returned header. Read reads from the current file in the tar archive. It returns (0, io.EOF) when it reaches the end of that file, until [Next] is called to advance to the next file. If the current file is sparse, then the regions marked as a hole are read back as NUL-bytes. Calling Read on special types like [TypeLink], [TypeSymlink], [TypeChar], [TypeBlock], [TypeDir], and [TypeFifo] returns (0, [io.EOF]) regardless of what the [Header.Size] claims. *Reader : io.Reader func NewReader(r io.Reader) *Reader
Writer provides sequential writing of a tar archive. [Writer.WriteHeader] begins a new file with the provided [Header], and then Writer can be treated as an io.Writer to supply that file's data. AddFS adds the files from fs.FS to the archive. It walks the directory tree starting at the root of the filesystem adding each file to the tar archive while maintaining the directory structure. Close closes the tar archive by flushing the padding, and writing the footer. If the current file (from a prior call to [Writer.WriteHeader]) is not fully written, then this returns an error. Flush finishes writing the current file's block padding. The current file must be fully written before Flush can be called. This is unnecessary as the next call to [Writer.WriteHeader] or [Writer.Close] will implicitly flush out the file's padding. Write writes to the current file in the tar archive. Write returns the error [ErrWriteTooLong] if more than Header.Size bytes are written after [Writer.WriteHeader]. Calling Write on special types like [TypeLink], [TypeSymlink], [TypeChar], [TypeBlock], [TypeDir], and [TypeFifo] returns (0, [ErrWriteTooLong]) regardless of what the [Header.Size] claims. WriteHeader writes hdr and prepares to accept the file's contents. The Header.Size determines how many bytes can be written for the next file. If the current file is not fully written, then this returns an error. This implicitly flushes any padding necessary before writing the header. *Writer : internal/bisect.Writer *Writer : io.Closer *Writer : io.WriteCloser *Writer : io.Writer func NewWriter(w io.Writer) *Writer
Package-Level Functions (total 3)
FileInfoHeader creates a partially-populated [Header] from fi. If fi describes a symlink, FileInfoHeader records link as the link target. If fi describes a directory, a slash is appended to the name. Since fs.FileInfo's Name method only returns the base name of the file it describes, it may be necessary to modify Header.Name to provide the full path name of the file. If fi implements [FileInfoNames] Header.Gname and Header.Uname are provided by the methods of the interface.
NewReader creates a new [Reader] reading from r.
NewWriter creates a new Writer writing to w.
Package-Level Constants (total 18)
FormatGNU represents the GNU header format. The GNU header format is older than the USTAR and PAX standards and is not compatible with them. The GNU format supports arbitrary file sizes, filenames of arbitrary encoding and length, sparse files, and other features. It is recommended that PAX be chosen over GNU unless the target application can only parse GNU formatted archives. Reference: https://www.gnu.org/software/tar/manual/html_node/Standard.html
FormatPAX represents the PAX header format defined in POSIX.1-2001. PAX extends USTAR by writing a special file with Typeflag TypeXHeader preceding the original header. This file contains a set of key-value records, which are used to overcome USTAR's shortcomings, in addition to providing the ability to have sub-second resolution for timestamps. Some newer formats add their own extensions to PAX by defining their own keys and assigning certain semantic meaning to the associated values. For example, sparse file support in PAX is implemented using keys defined by the GNU manual (e.g., "GNU.sparse.map"). Reference: http://pubs.opengroup.org/onlinepubs/009695399/utilities/pax.html
FormatUnknown indicates that the format is unknown.
FormatUSTAR represents the USTAR header format defined in POSIX.1-1988. While this format is compatible with most tar readers, the format has several limitations making it unsuitable for some usages. Most notably, it cannot support sparse files, files larger than 8GiB, filenames larger than 256 characters, and non-ASCII filenames. Reference: http://pubs.opengroup.org/onlinepubs/9699919799/utilities/pax.html#tag_20_92_13_06
Type flags for Header.Typeflag.
Type flags for Header.Typeflag.
Type '7' is reserved.
Type flags for Header.Typeflag.
Type flags for Header.Typeflag.
Types 'L' and 'K' are used by the GNU format for a meta file used to store the path or link name for the next file. This package transparently handles these types.
Type 'S' indicates a sparse file in the GNU format.
Type '0' indicates a regular file.
Deprecated: Use TypeReg instead.
Type 'g' is used by the PAX format to store key-value records that are relevant to all subsequent files. This package only supports parsing and composing such headers, but does not currently support persisting the global state across files.
Type 'x' is used by the PAX format to store key-value records that are only relevant to the next file. This package transparently handles these types.