Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: provide a way to set options or parameters #103

Closed
1 task done
pabloglombovsky opened this issue Oct 17, 2022 · 4 comments
Closed
1 task done
Assignees
Milestone

Comments

@pabloglombovsky
Copy link

Feature description

I need to avoid storing the NTFS extra field (where the last accessed, modified, and created times are stored). I saw that one way to do it in 7zip was to use the -mtc=off parameter.
I did not find any way to do it when creating a .zip file using this library. Is there any way?
Thanks

Additional context

No response

Code of Conduct

@rikyoz
Copy link
Owner

rikyoz commented Oct 23, 2022

Hi!

I did not find any way to do it when creating a .zip file using this library. Is there any way?

Unfortunately, no, it's not possible with the library's current versions (stable and beta).

However, I'll probably add this option to the library's next version.
The change should not take much effort in itself, but I'm thinking of providing a more general way to set custom 7-zip parameters.

@pabloglombovsky
Copy link
Author

pabloglombovsky commented Nov 21, 2022 via email

@rikyoz
Copy link
Owner

rikyoz commented Nov 22, 2022

Hi!

Do you know if there is a way using your library to bypass this?

Unfortunately, I don't think there's any way to bypass this limitation unless you directly modify the 7-zip source code.
I did some quick tests, and bit7z fails when using Asian/accentuated characters for .zip passwords: this is due to the internal calls to 7-zip failing, so I don't think there's much that bit7z can do in this case, I'm sorry!

@rikyoz rikyoz added this to the v4.0 milestone Dec 29, 2022
@rikyoz
Copy link
Owner

rikyoz commented Oct 1, 2023

Implemented in v4.0.0.

@rikyoz rikyoz closed this as completed Oct 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants