commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zbynek Vyskovsky (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COMPRESS-391) Zip entries alignment
Date Wed, 10 May 2017 19:57:04 GMT

    [ https://issues.apache.org/jira/browse/COMPRESS-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005301#comment-16005301
] 

Zbynek Vyskovsky commented on COMPRESS-391:
-------------------------------------------

The guys from Zip were quite quick, it's already published in preliminary version: https://support.pkware.com/display/PKZIP/Proposed+ZIP+Format+Specification+Additions

So probably worth sticking to this extra field and implement both reading and writing... What
do you think?


> Zip entries alignment
> ---------------------
>
>                 Key: COMPRESS-391
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-391
>             Project: Commons Compress
>          Issue Type: New Feature
>          Components: Archivers
>    Affects Versions: 1.13
>            Reporter: Zbynek Vyskovsky
>              Labels: features, github-import, patch
>             Fix For: 1.14
>
>
> Similarly to COMPRESS-390, there are requirements of the zip content to be mapped directly
into memory and therefore may require special alignment on the embedded files. E.g. libraries
may be aligned to page (4096-bytes) boundary, images on 4-bytes boundary etc. By alignment
it's meant the offset from the beginning of file where the actual data stream starts, not
the header.
> One of the cases was (still is?) Android APK for which zipalign utility was created.
> It would be useful if commons-compress ZipArchiveOutputStream supports something similar
directly in its API.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message