https://bugs.kde.org/show_bug.cgi?id=388232
--- Comment #2 from Peter Eszlari <peter.eszl...@gmail.com> --- > If I understand well, you want to generate a package that won't depend on > libudev, right? In the case of flatpak, yes. Flatpak runs the app in a sandbox, where it is not allowed to link against any libraries outside the sandbox (host). All libraries are either bundled with the app or provided by so called "runtimes", which also run in the sandbox. Communication with the host happens through dbus, X11 etc. > Yet, if you want to work on such patch, be my guest. Sorry, but this is way above my programming skills. :) > Not sure what should be done at Kaffeine in order to support it, but perhaps > the above patch would help, by forcing the usage of static libraries where > possible. No, for AppImage there should be no additional requirements, some just needs to do it. AppImges are just ISO images that get mounted by FUSE under /tmp and executed. They contain most of their dependencies, but not all. In the case of kaffeine one would include Qt, kf5-libs, vlc and libdvbv5, while not including low level stuff like glibc or libudev, but instead link against the libs provided by the host system. A lot of projects already provide AppImages: http://files.kde.org/kdenlive/release/Kdenlive-17.12.0d-x86_64.AppImage https://download.kde.org/stable/kdevelop/5.2.1/bin/linux/KDevelop-5.2.1-x86_64.AppImage https://download.kde.org/stable/krita/3.3.2/krita-3.3.2-x86_64.appimage You just have to chmod +x and ./prog.AppImage, that's all, no installation necessary. -- You are receiving this mail because: You are watching all bug changes.
