AppImage / AppImageKit

Package desktop applications as AppImages that run on common Linux-based operating systems, such as RHEL, CentOS, openSUSE, SLED, Ubuntu, Fedora, debian and derivatives. Join #AppImage on irc.libera.chat
http://appimage.org
Other
8.56k stars 546 forks source link

Investigate Freedesktop SDK #992

Open probonopd opened 4 years ago

probonopd commented 4 years ago

Investigate Freedesktop SDK to build what goes into an AppImage.

Freedesktop SDK claims to be distribution agnostic, desktop environment agnostic, and package format agnostic:

agnostic

probonopd commented 4 years ago

Note to self:

sudo add-apt-repository -y ppa:alexlarsson/flatpak
sudo apt update

sudo apt-get -y install flatpak
flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
flatpak install flathub org.freedesktop.Sdk//19.08
flatpak install flathub org.freedesktop.Platform//19.08
mksquashfs /var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/19.08/active/files/ org.freedesktop.Platform_19.08_x86_64.sqs

Further investigation blocked because I can't get Flatpak to work, as has been my problem since its inception.

probonopd commented 4 years ago

Reference: https://gitlab.com/freedesktop-sdk/freedesktop-sdk/issues/881

adds68 commented 4 years ago

I hope these answer some of your questions, i would encourage you to ask some questions in the channel on freenode (#freedesktop-sdk) also as some developers are more active there than on Gitlab.

probonopd commented 4 years ago

Thank you very much for your answers @Wetrain. Highly appreciated.

Especially the page you linked to,

The aim is to continuously update the runtime while keeping the ABI backward and forward compatible for as long as reasonably possible.

For the base runtime we expect multiple years of ABI stability to be feasible (parallel installation of multiple versions may occasionally be necessary for a few libraries). When an ABI break is required (e.g., C++ ABI break), the plan is to keep the previous branch maintained (at least for security updates) for two years.

is highly relevant to us. Will have to think about the implications a bit and discuss.

Would you happen to have a "hello world" example without BuildStream? (Nothing against it, in fact I heard about it today for the first time, but a lot of our users want to build on OBS, Travis CI, GitLab CI, Azure Pipelines, Jenkins, local machines, etc. and are not ready to jump to an entire new build setup)