Manual builds

loaih build can be used to build a single version of the AppImage.

CAVEATS

Considering that the goal of building a single version is very different from having a set of builds for a specific version, loaih v1.3.2 introduces two commands (build, documented here, and batch, documented in the relative page) to achieve both results.

From version 1.3.3, additionally, the default values for the available options for the single build (build verb) have been differentiated and simplified from the ones available for the set of builds (batch verb).

Hopefully, the chosen defaults would require the lowest number of options to be passed to the build command.

Examples

loaih build daily

Builds the daily build for today (reverting back to current if not existent).

loaih build 20231231 -u -l standard

Builds the daily version for December 31st, 2023 as updatable and with standard languages.

Options can also be specified with the longer version: for example, the option -s (which asks loaih to sign the AppImage) can also be specified as --sign, so the previous command could have looked as:

loaih build 20231231 --updatable --languages standard

For the full description of all the available options and their relative default values, please check out the inline help for the build verb:

loaih build --help

PLEASE BE AWARE that option names and short options have changed since v1.3.3, to the point this is indeed a breaking change.

Multiple single builds

Also the build verb supports multiple queries:

loaih build still,fresh

There's a little caveat, though: if the AppImage names of the requested versions will overlap (e.g. 7.5,7.5.9.2, both queries likely resulting in an AppImage file name of 'LibreOffice-7.5.9.2.basic-x86_64.AppImage'), only the result of the last query will survive the building process (all conflicting versions would be built, but the last one will likely overwrite the previous ones), unless the -c, --check option is used (and in this case, just the first one will survive and the rest would be skipped).

Default working paths

If not specified otherwise, a normal run would build the AppImage in the directory in which the command has been run and it will download all the required files in a downloads sub-folder, that will be created if missing and removed entirely at the end of the build process (unless -k option is used - see below).

You can specify a different result directory with the -r option (e.g. -r /home/myuser/Desktop), a different download directory with -d option (e.g. -d /tmp/downloads) and keep the whole download folder with the -k option (-k is the short version of the option --keep-downloads, which should be quite explicit at this point; use it if you would like to build the same version but with different options consecutively).

Home — Prerequisites — Installation — Core concepts — Usage - versions — Usage - batch build