You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2010/05/09 22:20:48 UTC
[jira] Created: (COMPRESS-109) Tar implementation does not support
Pax headers
Tar implementation does not support Pax headers
-----------------------------------------------
Key: COMPRESS-109
URL: https://issues.apache.org/jira/browse/COMPRESS-109
Project: Commons Compress
Issue Type: Bug
Reporter: Sebb
The tar implementation does not currently support Pax extended or global headers; they are treated as normal files.
See http://www.opengroup.org/onlinepubs/009695399/utilities/pax.html for details.
Pax headers have a different linkType (typeflag) of 'g' or 'x', so can easily be detected.
It would be quite a bit of work to process all the possible headers, so perhaps it would be worth providing an initial implementation that just ignores them?
This should probably be an optional setting.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (COMPRESS-109) Tar implementation does not support
Pax headers
Posted by "Sebb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COMPRESS-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sebb resolved COMPRESS-109.
---------------------------
Fix Version/s: 1.1
Resolution: Fixed
Added support for reading Pax headers.
Note: global pax headers are not supported.
No support for writing pax headers.
> Tar implementation does not support Pax headers
> -----------------------------------------------
>
> Key: COMPRESS-109
> URL: https://issues.apache.org/jira/browse/COMPRESS-109
> Project: Commons Compress
> Issue Type: Bug
> Reporter: Sebb
> Assignee: Sebb
> Fix For: 1.1
>
>
> The tar implementation does not currently support Pax extended or global headers; they are treated as normal files.
> See http://www.opengroup.org/onlinepubs/009695399/utilities/pax.html for details.
> Pax headers have a different linkType (typeflag) of 'g' or 'x', so can easily be detected.
> It would be quite a bit of work to process all the possible headers, so perhaps it would be worth providing an initial implementation that just ignores them?
> This should probably be an optional setting.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.