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

Binaries #63

Closed
KOLANICH opened this issue Dec 10, 2016 · 7 comments
Closed

Binaries #63

KOLANICH opened this issue Dec 10, 2016 · 7 comments
Milestone

Comments

@KOLANICH
Copy link

KOLANICH commented Dec 10, 2016

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.

@GreyCat
Copy link
Member

GreyCat commented Dec 10, 2016

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?

@KOLANICH
Copy link
Author

KOLANICH commented Dec 10, 2016

and we publish all unstable .msi builds as AppVeyor artifacts.

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.

@GreyCat
Copy link
Member

GreyCat commented Dec 10, 2016

It's nice! I guess linux users can just unpack the msi to get the jar file.

So far, none of the Linux users complained — I guess git clone + sbt stage is something that average Linux user can do. But point taken, there are plans to publish .zip + .deb artifacts as well that I'll publish soon in #62.

It even may be better to just supply a jar file since it doesn't require installation.

We don't build fat jars, and kaitai_struct.jar alone is not enough to work properly on an average system.

Please add the link to the download section of the website.

Um, what exactly is missing?

download_msi

@KOLANICH
Copy link
Author

Um, what exactly is missing?

Links in Universal .zip and Linux .dev sections are missing.

@KOLANICH
Copy link
Author

KOLANICH commented Feb 17, 2018

@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.

@KOLANICH KOLANICH reopened this Feb 17, 2018
@GreyCat
Copy link
Member

GreyCat commented Apr 12, 2018

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.

@GreyCat GreyCat added this to the v0.9 milestone Mar 28, 2019
@GreyCat
Copy link
Member

GreyCat commented Apr 18, 2019

Finally, seems to be done.

@GreyCat GreyCat closed this as completed Apr 18, 2019
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