Skip to content

Conversation

@sensslen
Copy link
Contributor

I certify that I own, and have sufficient rights to contribute, all source code and related material intended to be compiled or integrated with the source code for the SharpZipLib open source product (the "Contribution"). My Contribution is licensed under the MIT License.

The proposed fix does fix an immediate problem (namely the specified root path of a tar archive not being respected on a unix system). However I feel the correct solution would be to use path's as they are used on the operating system running and doing the conversion at the last point before writing it to the file. This would remove a lot of similar hacks.

This PR resolves #580

0xced and others added 7 commits December 7, 2020 16:47
This is a very rough first pass at adding async support to ZipOutputStream.

All method doing synchronous stream writes have been duplicated with an asynchronous counterpart, starting from `ZipOutputStream.PutNextEntryAsync()`. Unfortunately, this makes a lot of duplicated code but is unavoidable to have both sync + async code paths.

.NET Standard 2.1 has been added to the target frameworks. It's required to get full async support with `Stream.DisposeAsync()`.

New unit tests must be written to cover the new async code paths.

Fixes #223
…ut code duplication

- Add unit test that tests the compression and extraction
@sensslen sensslen closed this Feb 17, 2021
@sensslen
Copy link
Contributor Author

close PR, as the proposed fix causes Issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Linux: Tar archive file root path is not stripped from file paths

3 participants