Hm, no quick explanation at least.
Do you get any kind of output or error message when you launch the appimage from the terminal?
We intentionally build the AppImage and the Flatpak releases on Ubuntu 16.04/Xenial, to ensure it runs on (even relatively ancient but) still supported Ubuntu versions, so at least that shouldn't be the cause.
librewolf.cfg– if you want to use / change those settings, you need to edit
/usr/lib/librewolf/librewolf.cfgdirectly (more complex if using appimage or flatpak, I think); the settings to look for should be
Interesting distro ^^
Is internet access available when pulling the required sources, or would those have to be available locally beforehand?
Looking at the package system, it seems like it should be easiest to start from the PKGBUILD, as the KISS build system also seems to pretty much "just a script" – so we could either pull in all the sources directly as well, or provide them offline with just a few changes.
librewolf.desktop, for x86_64 at least) directly and follow allong. prepare, build and package are just functions executed in that order, and the only other specialty is that some variables (
$CARCH (architecture: aarch64, x86_64 etc),
$srcdir (pkgdir is the "output directory" that gets packaged; srcdir is the working directory, where the sources are).
nope, just extends the string in the variable, instead of other ways to avoid having one looooong line ^^
remove_addons.patchremoves some addons which might be undesired / be used to collect data, by not having them built and removing some code referencing them.
Hund on FreenodeHi!
@freenode_Hund:matrix.orgwas kicked by
Telegram Bridge("This chat does not have a bot relaying messages for unauthenticated users.").