Enable settings by default in Appimage and FlatPak

Crude solution, but this way everything else remains "as is",
so once we tackle the issues with the toggle-settings-script not working
in all situations and re-introduce it, we can do easier switch to that
instead.

Fix (partial only) for #105.

binary_tarball/scripts/5_Configure_Binary_Tarball.sh

@@ -17,11 +17,16 @@ tar -xf $BINARY_TARBALL -C $_EXTRACTED_TARBALL_FOLDER/..;
 printf "\nCopying librewolf settings to extracted binary tarball\n";
 
 git clone $_SETTINGS_REPO $_EXTRACTED_TARBALL_FOLDER/settings;
+# no need to keep that in there
+rm -rf "${_EXTRACTED_TARBALL_FOLDER}/settings/.git";
 cp $TOGGLE_SETTINGS_SCRIPT $_EXTRACTED_TARBALL_FOLDER/settings;
 cp $LAUNCHER_SCRIPT $_EXTRACTED_TARBALL_FOLDER/launch_librewolf.sh;
 
+# Somewhat crude workaround to use settings per default
+# until we've worked out how to use `--install-settings` with links
+# in all major packages instead
+cp $_EXTRACTED_TARBALL_FOLDER/settings/* $_EXTRACTED_TARBALL_FOLDER;
+
 # Repacks the binary tarball
 printf "\nRecompressing binary tarball\n";
 tar -jvcf $BINARY_TARBALL -C $_EXTRACTED_TARBALL_FOLDER .;
-
-

content/launch_librewolf.sh

@@ -27,6 +27,3 @@ export SNAP_NAME="firefox";
 # Launches librewolf
 chmod +x $INSTALL_FOLDER/librewolf;
 $INSTALL_FOLDER/librewolf "$@";
-
-
-