-
Notifications
You must be signed in to change notification settings - Fork 51
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
Improved compatibility with Windows by providing zip binary archives #321
Comments
Closed by accident when going through my list of open issues. Apologies for any confusion. |
@mstruebing I may be able to provide a PR for this but just to be sure I am not overlooking anything too obvious … the relevant change would be in the Makefile and probably involve a Windows vs. everything else check, right? |
@Okeanos yes you are right. Except you would want to compress all binaries as zips. |
…cker#321) This adds a zip archive to the output of the compress-all-binaries sub-task in order to provide better compatiblitiy with Windows. Windows does not come with the ability to handle tar.gz (until now the only output format) and, hence, users cannot easily use the prebuilt binaries distributed via GitHub. Further integration into, for example, the winget community packages is also prevented by this. Zip was chosen as an _additional_ output format in order to not create an unexpected/breaking change for consumers of the existing tar.gz format. Windows is not handled specifically here in order to keep the process of providing build artifacts as simple as possible.
This adds a zip archive to the output of the compress-all-binaries sub-task in order to provide better compatiblitiy with Windows. Windows does not come with the ability to handle tar.gz (until now the only output format) and, hence, users cannot easily use the prebuilt binaries distributed via GitHub. Further integration into, for example, the winget community packages is also prevented by this. Zip was chosen as an _additional_ output format in order to not create an unexpected/breaking change for consumers of the existing tar.gz format. Windows is not handled specifically here in order to keep the process of providing build artifacts as simple as possible.
This issue should probably be closed as #362 have been merged? |
As very briefly mentioned in #204
It would be very, very cool if you could provide Windows binary releases as
.zip
archive instead of.tar.gz
– Windows isn't natively able to unpack/work with.tar.gz
. This makes it especially troublesome because tools such aswinget
are also not able to deal with.tar.gz
either.Providing
.zip
files would open up a lot of additional fancy integration possibilities via e.g.winget
and related tooling making adoption on Windows way easier and nicer.The text was updated successfully, but these errors were encountered: