[Release] Integrating in appveyor the pre-compiled package for Linux

[alacasta]

What?

As a Linux User, I want to have the QJournalctl application ready to be used without needing to compile it.

How?

So far, it is already integrated such feature at appveyor for windows. It is now possible to get it from https://ci.appveyor.com/project/pentix/qjournalctl/builds/31801115 > artifacts > release.zip. (i.e. https://ci.appveyor.com/api/buildjobs/mo40lkrya80svedb/artifacts/release.zip)

It is possible to configure appveyor to have both, the release for Linux and for Windows. Also, it is possible to connect it with Github to release them into the released at Github, but probaby this step is better to handle manualy until #47 is solved

[pentix]

Having a pre-compiled package would be nice! A lot has already been discussed in #37 but since the main point of your issue is to integrate it in AppVeyor (which is a great idea!) I'll let this issue open.

#37 is definitely a dependency and its solution needs to automatically create .deb, flatpak packages, etc. before being able to integrate it with AppVeyor and GitHub.

[alacasta]

Thanks! I'd really love this...
My point is that #37 was actually related to find a solution to not needing to build the application but instead, have it ready-to-use. Don't you think both, this and #37 more or less the same?
There are many different options to reach it, but the simpler one would be to have the package distributed as it is now for Windows: The binary and its dependencies all-in-packaged.

How do you see if i try to increase the appveyor.yml file so that bot, Linux and Windows packages are released?

[alacasta]

Hello @pentix
I didn't know that there is an equivalent to windeployqt for Linux which is based on AppImage: https://github.com/probonopd/linuxdeployqt

Also there is an example for integrating it in Travis https://github.com/probonopd/linuxdeployqt#using-linuxdeployqt-with-travis-ci

I think that this is a good approach to have the release available for any Linux distro. Even more important, is the fact of integrating also the Qt depenedencies, which makes the .deb package unusable for an external user.