-
Notifications
You must be signed in to change notification settings - Fork 6
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
Remove zip build dependency #77
Conversation
35b9b0b
to
9605444
Compare
Hey @tuurep let me know if this works for you and Arch has |
9605444
to
eb537d4
Compare
Lets be careful with this I think there's a reason that the AUR system uses specifically ^ warning - I don't really know what I'm talking about but here goes some testing and observations: Case: tar
File type:
Size:
Trying to extract using
Case: bsdtar
File type:
Size:
Trying to extract using
|
Oh, very interesting and also strange... On my system it's different » tar --auto-compress --create --file test.zip static
» file test.zip
test.zip: Zip archive data, at least v2.0 to extract, compression method=store
» du -sh test.zip
872K test.zip
» du -sh static
1.2M static and then the unzipping definitely works through the Node library. But actually, running
so it seems my |
Ohh... very good that you found that out |
Haha yes maybe but now I'm more confused than before. Does the linux CI-build on this branch work for you? That way we could take a guess on what kind of |
But anyways, I guess we can just close this PR then and leave it as it was? Or do you think it's worth it to further investigate? Seems like the intersection of tools that
is a very small if not empty set |
Yeah it makes sense because Linux tar = GNU tar *(usually) Same goes for a bunch of tooling: |
Makes sense. On macOS we have the GNU tools (if at all) with a Anyways, what do you think about dropping this vs. trying to find a solution that fulfills the three cases?
|
Yeah here's what I think: I can use |
Oki sounds good! Closing this then |
Close #76