[
https://issues.apache.org/jira/browse/SANDBOX-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672680#action_12672680
]
Stefan Bodewig commented on SANDBOX-282:
----------------------------------------
to tell the truth, we probably don't know exactly what we implement 8-)
The tar classes have been in Ant since early 2000 and it has never been clearly
documented what spec they are based on. I know we support part of the GNU
extensions (long filenames).
POSIX would be good, agreed.
> TAR formaT unspecified
> ----------------------
>
> Key: SANDBOX-282
> URL: https://issues.apache.org/jira/browse/SANDBOX-282
> Project: Commons Sandbox
> Issue Type: Bug
> Components: Compress
> Affects Versions: Nightly Builds
> Environment: I use win xp sp3, but this is probably irrelevant.
> Reporter: Sam Smith
>
> 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.
