| Line 1... |
Line 1... |
| 1 |
% File src/library/utils/man/tar.Rd
|
1 |
% File src/library/utils/man/tar.Rd
|
| 2 |
% Part of the R package, http://www.R-project.org
|
2 |
% Part of the R package, http://www.R-project.org
|
| 3 |
% Copyright 2009-12 R Core Team
|
3 |
% Copyright 2009-13 R Core Team
|
| 4 |
% Distributed under GPL 2 or later
|
4 |
% Distributed under GPL 2 or later
|
| 5 |
|
5 |
|
| 6 |
\name{tar}
|
6 |
\name{tar}
|
| 7 |
\alias{tar}
|
7 |
\alias{tar}
|
| 8 |
\title{
|
8 |
\title{
|
| Line 83... |
Line 83... |
| 83 |
\item The handling of file paths of more than 100 bytes. These were
|
83 |
\item The handling of file paths of more than 100 bytes. These were
|
| 84 |
unsupported in early versions of \command{tar}, and supported in one
|
84 |
unsupported in early versions of \command{tar}, and supported in one
|
| 85 |
way by POSIX \command{tar} and in another by GNU \command{tar} and
|
85 |
way by POSIX \command{tar} and in another by GNU \command{tar} and
|
| 86 |
yet another by the POSIX \command{pax} command which
|
86 |
yet another by the POSIX \command{pax} command which
|
| 87 |
recent\command{tar} programs often support. The internal
|
87 |
recent\command{tar} programs often support. The internal
|
| - |
|
88 |
implementation warns on paths of more than 100 bytes,
|
| 88 |
implementation uses the \sQuote{ustar} way from the 1998 POSIX
|
89 |
uses the \sQuote{ustar} way from the 1998 POSIX
|
| 89 |
standard which supports up to 256 bytes (depending on the path: in
|
90 |
standard which supports up to 256 bytes (depending on the path: in
|
| 90 |
particular the final component is limited to 100 bytes), and warns
|
91 |
particular the final component is limited to 100 bytes) if possible,
|
| 91 |
on paths of more than 100 bytes.
|
92 |
or the GNU way (which is widely supported).
|
| 92 |
|
93 |
|
| 93 |
Most formats do not record the encoding of file paths.
|
94 |
Most formats do not record the encoding of file paths.
|
| 94 |
|
95 |
|
| 95 |
\item (File) links. \command{tar} was developed on an OS that used
|
96 |
\item (File) links. \command{tar} was developed on an OS that used
|
| 96 |
hard links, and physical files that were referred to more than once
|
97 |
hard links, and physical files that were referred to more than once
|
| Line 102... |
Line 103... |
| 102 |
not support them: for regular files, at least, file copies can be
|
103 |
not support them: for regular files, at least, file copies can be
|
| 103 |
used.
|
104 |
used.
|
| 104 |
|
105 |
|
| 105 |
Names of links in the \sQuote{ustar} format are restricted to 100
|
106 |
Names of links in the \sQuote{ustar} format are restricted to 100
|
| 106 |
bytes. There is an GNU extension for arbitrarily long link names,
|
107 |
bytes. There is an GNU extension for arbitrarily long link names,
|
| 107 |
but \command{bsdtar} does not read. As from \R 3.0,0 the internal
|
108 |
but \command{bsdtar} does not read. As from \R 2.15.3 the internal
|
| 108 |
method uses the GNU extension, with a warning.
|
109 |
method uses the GNU extension, with a warning.
|
| 109 |
|
110 |
|
| 110 |
\item Header fields, in particular the padding to be used when
|
111 |
\item Header fields, in particular the padding to be used when
|
| 111 |
fields are not full or not used. POSIX did define the correct
|
112 |
fields are not full or not used. POSIX did define the correct
|
| 112 |
behaviour but commonly used implementations did (and still do)
|
113 |
behaviour but commonly used implementations did (and still do)
|
The R Project SVN
R