Trigger appimagetool build

[probonopd]

Try to trigger an appimagetool build in addition to uploading the continuous build to GitHub Releases.

Thus, when a change in this repository prevents the appimagetool AppImage from being built correctly, we will know immediately rather than a few months down the line.

This in part might have prevented

• appimagetool has old URL, does not check runtime size nor HTTP status code appimagetool#58

from having happened unnoticed.

[probonopd]

TypeError: Cannot read properties of undefined (reading 'token')

How to do this correctly?

[TheAssassin]

We've talked about this recently and I absolutely hate the idea. Plus, the token you try to use isn't even authorized to do so.

appimagetool automatically downloads the latest runtime anyway.

[TheAssassin]

P.S.: If testing is your intention, you can clone appimagetool's repository here, too, and run the build script accordingly.

[probonopd]

We've talked about this recently and I absolutely hate the idea.

Can you remind me of why you don't like this? Maybe combining the repos of type2-runtime and appimagetool would be a more elegant solution then?

appimagetool automatically downloads the latest runtime anyway.

Which is what I still think is too fragile, especially when the two are not in sync (which can happen due to developer error or simply because the user uses an older appimagetool version...)

[TheAssassin]

Maybe combining the repos of type2-runtime and appimagetool would be a more elegant solution then?

Yet again, discussed and rejected. That's what we had, and it's what we never want to go back to.

[TheAssassin]

You should open an issue by the way.

[probonopd]

You should open an issue by the way.

Open an issue for what? Everything I propose doesn't seem to be liked by you (triggering builds in another repo automatically, merging repos). For bundling the runtime in the linuxdeployqt AppImage there is already an issue open,

• Consider to bundle the runtime appimagetool#61

[TheAssassin]

The issue here is that this discussion is likely going to be lost in a closed PR.

Everything I propose doesn't seem to be liked by you

We've discussed every single option and I've always had the better arguments after all. It's tiring to reiterate over each of them every time some issue surfaces. It's nothing I'd do in a project because it's not productive.

It seems that the issue here is missing documentation from meetings we had...