question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Update check on Ubuntu points to Appimage instead of deb file

See original GitHub issue

I’ve just checked updates and clicked Download button. I was directed to download cerebro-0.2.6-x86_64.AppImage file, while expectation is to download cerebro_0.2.6_amd64.deb (current version 0.2.5 is installed from deb file). Is this something that might be improved?

Issue Analytics

  • State:open
  • Created 7 years ago
  • Reactions:1
  • Comments:10 (4 by maintainers)

github_iconTop GitHub Comments

2reactions
maximbazcommented, Feb 13, 2017

snaps are also supported other distros, I think devs want them to be as universal as AppImage. However this particular format is built by Ubuntu folks, and so they naturally target Ubuntu first. In reality I haven’t heard anyone outside of Ubuntu using snaps (yet?).

I’d say ideally you should provide all 4, Snaps / Flatpack / AppImage / deb, plus sources. With these four you would literally cover almost everyone’s needs, and the rest will gladly build from sources. Electron-builder doesn’t support Flatpack yet though.

When choosing a default, consider what benefits you could achieve by that. In my mind, you definitely want to ensure that as many people as possible use the latest version, and thus do not experience and do not report bugs that have already been fixed. This means prioritizing the formats that provides either fully automatic updates or native integration with OS package manager. But that also means investing time to investigate how exactly to provide this (for .deb you would need to provide PPA, for others I imagine there’s something else to configure).

1reaction
maximbazcommented, Feb 13, 2017

Ubuntu is moving away from .deb though, the future standard will be snap packages. Here’s why. Internally .deb files are still used as I understand, but the end-users will be using snaps.

Snaps / Flatpack / AppImage are three different formats with a very similar purpose, to improve packaging and distribution of applications. Differences are listed for example here.

How to choose today:

  • If the upgrade process is manual, use AppImage as it is simpler and independent of Linux distro.
  • If a native integration with OS package manager is desired (so that updates are coming automatically), the format depends on the OS. For Ubuntu, that could only be snaps or .deb.
Read more comments on GitHub >

github_iconTop Results From Across the Web

How do I update appimages? - Ask Ubuntu
Run AppImageUpdate and select the AppImage application you wish to check for update availability from the file chooser dialog.
Read more >
How To Use AppImage in Linux [Complete Guide] - It's FOSS
Brief: This AppImage tutorial shows you how to use AppImage to install software and how to remove the applications it installed.
Read more >
Deb package vs Appimage #2634 - Ultimaker/Cura - GitHub
Hello, I need to install Cura3 on every computers (in a school) using Debian. Appimage is not very simple to use : no...
Read more >
pkg2appimage - AppImage documentation
yml file that describes how to build an AppImage for app , being able to reuse pre-built binaries, e.g. from Debian packages, both...
Read more >
Why doesn't everyone use appimages instead of .deb, .rpm or ...
provider and update reliability: going off the point above, ... The benefits of using packages rather than AppImages comes down to package ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found