[
https://issues.apache.org/jira/browse/COMPRESS-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13580015#comment-13580015
]
Gili edited comment on COMPRESS-136 at 2/16/13 8:14 PM:
--------------------------------------------------------
I agree, with the following additions.
# You should include zip and gzip since they support POSIX permissions.
# For zip, in particular, you should return entries using
ZipFile.getEntriesInPhysicalOrder() otherwise files get created after their
parent directories and we are forced to create those directories before knowing
their POSIX permissions.
# Handle recursive types such as .tar.gz, unpacking .gz then .tar automatically
or provide a mechanism to easily implement this in two steps.
Plexus Archiver has a very nice interface for this. You supply a source and
target path, and invoke extract(). That's it. Recursive archives and POSIX
permissions are handled automatically under the hood.
was (Author: cowwoc):
I agree, with the following additions.
# You should include zip and gzip since they support POSIX permissions.
# For zip, in particular, you should return entries using
ZipFile.getEntriesInPhysicalOrder() otherwise files get created after their
parent directories and we are forced to create those directories before knowing
their POSIX permissions.
> Create common POSIXArchiveEntry for use with tar/cpio/dump
> ----------------------------------------------------------
>
> Key: COMPRESS-136
> URL: https://issues.apache.org/jira/browse/COMPRESS-136
> Project: Commons Compress
> Issue Type: Improvement
> Components: Archivers
> Reporter: Bear Giles
> Priority: Minor
> Fix For: 2.0
>
> Attachments: COMPRESS-136-Owner.patch
>
>
> There's currently a top-level ArchiveEntry but many archivers are for POSIX
> (or POSIX-like) filesystems with standard attributes - ownership,
> permissions, access times, etc. By creating a common ArchiveEntry class for
> these attributes it will be much easier to write archive-agnostic extraction
> software. (Many of the existing methods should be marked 'deprecated' but
> left in place indefinitely.)
> I have a prototype of this class in my dump patch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
