-
Notifications
You must be signed in to change notification settings - Fork 200
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
Binaries #63
Comments
Um, we already have binaries published for releases at BinTray (see downloads links from our website), and we publish all unstable .msi builds as AppVeyor artifacts. The only thing I can think of is publishing unstable .zip / .deb artifacts — you mean that? |
It's nice! I guess linux users can just unpack the msi to get the jar file. It even may be better to just supply a jar file since it doesn't require installation. Please add the link to the download section of the website. |
So far, none of the Linux users complained — I guess
We don't build fat jars, and kaitai_struct.jar alone is not enough to work properly on an average system.
Um, what exactly is missing? |
Links in Universal .zip and Linux .dev sections are missing. |
@GreyCat, how about fixing building of nightly packages for linux distros on bintray? I don't want to rebuild KSC on travis and I don't want to use lessmsi (because it requires .net runtime which is large) or wine (is large itself) there. Also IMHO it's better to have it rather than perverse with unpacking msi. |
Since ~2018-02-28 (as seen in commits like these), we're publishing unstable Debian packages to https://bintray.com/kaitai-io/debian_unstable repo. I guess all that's left is adding relevant link to website. |
Finally, seems to be done. |
I think that we should supply binary packages. This can be done using Travis CI.
1 Build binary packages in Travis CI. They are built anyway, all what you need is to package build results into packages.
2 Upload them into repos' Releases and anywhere else using the Travis feature to supply private data in encrypted form.
The text was updated successfully, but these errors were encountered: