[
https://issues.apache.org/jira/browse/COMPRESS-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved COMPRESS-17.
------------------------------------
Resolution: Fixed
For the record: the package really only supports the old pre-POSIX ustar format
and the GNU mode for long files names is actually "oldgnu" which is deprecated
by GNU tar by now.
Yes, we should implement full POSIX tar compliance one day - it just a matter
of finding the time to code it ...
svn revision 909051 documents the supported format.
> TAR format unspecified
> ----------------------
>
> Key: COMPRESS-17
> URL: https://issues.apache.org/jira/browse/COMPRESS-17
> Project: Commons Compress
> Issue Type: Bug
> Environment: I use win xp sp3, but this is probably irrelevant.
> Reporter: Sam Smith
> Fix For: 1.1
>
>
> The TarArchive*putStream and Tar*putStream (e.g.
> TarInputStream/TarOutputStream) javadocs say nothing about which specific TAR
> format(s) they support.
> They merely use the phrase "UNIX tar archive" which is WAY too generic of a
> statement.
> Here are some discussions on the various TAR formats:
> http://www.gnu.org/software/tar/manual/html_section/Formats.html
> http://leaf.dragonflybsd.org/cgi/web-man?command=tar§ion=5
> I HIGHLY URGE YOU TO SUPPORT THE POSIX.1-2001 SPECIFICATION, SINCE IT SOLVES
> SO MANY ISSUES (e.g. it supports unlimited path lengths and file sizes).
> Corollary, once you decide which TAR formats to support, this needs to be
> added to the javadocs. Make sure that the javadocs discuss all limitations
> for whatever format(s) are supported (especially on pathlengths, file sizes,
> character sets, etc). Also make sure and include a hyperlink to a webpage
> that describes the format standards.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
