Skip to content

Generate and upload AppImage #60

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

Closed
wants to merge 1 commit into from
Closed

Conversation

probonopd
Copy link

@probonopd probonopd commented Apr 21, 2019

This PR, when merged, will compile this application on Travis CI upon each git push, and upload an AppImage to your GitHub Releases page.

Providing an AppImage would have, among others, these advantages:

  • Applications packaged as an AppImage can run on many distributions (including Ubuntu, Fedora, openSUSE, CentOS, elementaryOS, Linux Mint, and others)
  • One app = one file = super simple for users: just download one AppImage file, make it executable, and run
  • No unpacking or installation necessary
  • No root needed
  • No system libraries changed
  • Works out of the box, no installation of runtimes needed
  • Optional desktop integration with appimaged
  • Optional binary delta updates, e.g., for continuous builds (only download the binary diff) using AppImageUpdate
  • Can optionally GPG2-sign your AppImages (inside the file)
  • Works on Live ISOs
  • Can use the same AppImages when dual-booting multiple distributions
  • Can be listed in the AppImageHub central directory of available AppImages
  • Can double as a self-extracting compressed archive with the --appimage-extract parameter
  • No repositories needed. Suitable/optimized for air-gapped (offline) machines

Here is an overview of projects that are already distributing upstream-provided, official AppImages.

PLEASE NOTE: For this to work, you need to set up GITHUB_TOKEN in Travis CI for this to work; please see https://github.com/probonopd/uploadtool.

If you have questions, AppImage developers are on #AppImage on irc.freenode.net.

cc @zdenop @marathone

@probonopd
Copy link
Author

An AppImage for testing is available at https://github.com/probonopd/scantailor-advanced/releases.

@4lex4
Copy link
Owner

4lex4 commented May 12, 2020

Rejected due to #69, #124

Resume:

  1. Qt theming is broken if AppImage is launched in an environment different from that it was built on.
  2. The same for Qt High DPI displays support.

@4lex4 4lex4 closed this May 12, 2020
@probonopd
Copy link
Author

probonopd commented May 14, 2020

Then we should fix those things, shouldn't we @4lex4? ;-)

Qt theming is broken if AppImage is launched in an environment different from that it was built on.

I'd say: Cosmetic, hardly a reason not to offer an AppImage at all.

But anyhow:
With some fine-tuning, it can probably be made work if we know what "broken" exactly is referring to. For example, the Scribus (also Qt based) AppImage theming looks very native on a Xubuntu (Gtk) system.

If you want KDE theming, then as I wrote in #69 probably some plugin for KDE theming would need to be bundled inside the AppImage.

The same for Qt High DPI displays support

Please elaborate. In #124 someone says that the fonts are "too small" in some old build of the AppImage.

I wonder whether e.g., the Scribus AppImage is exhibiting the same issues, as it is also a Qt-based applications used by many design-affine users every day. @aoloe do those concerns sound familiar to you?

@aoloe
Copy link

aoloe commented May 15, 2020

i have the feeling that the appimage behaves correctly in an hdpi setting.

but since i have custom settings in place to run the normal scribus i think that i'm not the right one to judge about it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants