You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it will be useful to document how to create a reproducible ZIP file - i.e. a ZIP file that has identical content as long as the source files have not changed.
This is very useful for build services and all kinds of cache management services, and its pretty easy to do - you just have to zero out the time field.
If PR #365 was rejected and closed, should this issue also be closed for v3.x ?
(It might have been added to the v2.x docs, but would then likely need to have been removed for 3.0.)
While at that time, the close comment at #365 made sense to me, I think there is still a use case for forcing the file time to zero - to handle cases where the last modified timestamp changes without the file content changing: some processes can cause multiple source copies to have differing time stamps for the same content.
Its not high priority for me as I'm already doing what I need to be doing, but I thought that other people may be interested in documenting the process.
I think it will be useful to document how to create a reproducible ZIP file - i.e. a ZIP file that has identical content as long as the source files have not changed.
This is very useful for build services and all kinds of cache management services, and its pretty easy to do - you just have to zero out the time field.
See here for a discussion
The text was updated successfully, but these errors were encountered: