Edited existing pages, drafted start for Batch.
Emiliano Vavassori
parent
a954807a8d
commit
3d889d23d8
5
Batch.md
5
Batch.md
|
|
@ -1,6 +1,9 @@
|
|||
# Batch building #
|
||||
|
||||
TODO
|
||||
Batch building is used to provide a set of AppImages for a specific version of
|
||||
LibreOffice (and it is the mechanism used to provide AppImage releases on the
|
||||
[official website](https://www.libreoffice.org/download/appimage/)).
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
|
|
|||
36
Build.md
36
Build.md
|
|
@ -17,7 +17,7 @@ Hopefully, the chosen defaults would require the lowerst number of options to
|
|||
be passed to the `build` command.
|
||||
|
||||
|
||||
## Example runs ##
|
||||
## Examples ##
|
||||
|
||||
loaih build daily
|
||||
|
||||
|
|
@ -30,26 +30,46 @@ 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 the command to sign the AppImage) can also be
|
||||
specified as `--sign`.
|
||||
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
|
||||
1.3.3, to the point this is indeed a **breaking change**.
|
||||
|
||||
|
||||
## Multiple single builds ##
|
||||
|
||||
Also the `build` verb supports multiple query:
|
||||
|
||||
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`), only the last in the 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` subfolder that created if missing and will be
|
||||
removed entirely at the end of the build.
|
||||
required files in a `downloads` subfolder 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 downloads with the `-k` option (`-k` for
|
||||
*keep* downloads, for example if you plan to run different options for the
|
||||
same query).
|
||||
`-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](Home.md) — [Prerequisites](Prerequisites.md) — [Installation](Install.md) — [Usage - versions](Version.md) — [Usage - batch build](Batch.md)
|
||||
|
|
|
|||
51
Version.md
51
Version.md
|
|
@ -1,31 +1,30 @@
|
|||
# Usage - versions #
|
||||
|
||||
`loaih` can help to find out information about specific LibreOffice versions;
|
||||
this happens because the script parses the official download page and/or
|
||||
infers from some other sources.
|
||||
`loaih` can be used to find out information about a specific LibreOffice versions; the script parses the [official LibreOffice download page](https://www.libreoffice.org/download/download-libreoffice/) and, in specific cases like daily builds, infers their availability from other known repositories.
|
||||
|
||||
`loaih getversion` helps to find those information:
|
||||
`loaih getversion` can be used as:
|
||||
|
||||
loaih getversion 7.6.2
|
||||
loaih getversion 5.4
|
||||
|
||||
For example would reply with the following information:
|
||||
to receive the following information:
|
||||
```
|
||||
query: 7.6.2
|
||||
version: 7.6.2.1
|
||||
x86: -
|
||||
x86_64: https://downloadarchive.documentfoundation.org/libreoffice/old/7.6.2.1/deb/x86_64/
|
||||
query: 5.4
|
||||
version: 5.4.7.2
|
||||
x86: https://downloadarchive.documentfoundation.org/libreoffice/old/5.4.7.2/deb/x86/
|
||||
x86_64: https://downloadarchive.documentfoundation.org/libreoffice/old/5.4.7.2/deb/x86_64/
|
||||
```
|
||||
|
||||
The *query* line would report each argument for the `getversion` verb; the
|
||||
*version* is the full version of the LibreOffice version matching the query;
|
||||
the *x86* and *x86_64* would provide URLs to download all the needed archives
|
||||
to build the AppImage (but do not worry, you don't necessarily need to do it
|
||||
by hand).
|
||||
The *query* line would report each argument for the `getversion` verb (see
|
||||
below in *Multiple queries*); the *version* is the full version of
|
||||
LibreOffice matching the query; the *x86* and *x86_64* would provide URLs to
|
||||
download all the needed archives to build the AppImage.
|
||||
|
||||
## Textual queries ##
|
||||
|
||||
`loaih` supports textual queries, when you want to find the latest version of
|
||||
some categories of LibreOffice. The following textual queries are supported:
|
||||
some specific categories of LibreOffice releases.
|
||||
|
||||
The following textual queries are supported:
|
||||
|
||||
* `fresh` and `still`: these are the stable release versions for LibreOffice;
|
||||
* `prerelease`: refers to the last prerelease version published on the
|
||||
|
|
@ -38,22 +37,28 @@ today, and the daily build for yesterday;
|
|||
number); for a working example, 20231231 for the December 31st, 2023.
|
||||
|
||||
|
||||
## Fallback to current for daily builds ##
|
||||
## Fallback to current for missing daily versions ##
|
||||
|
||||
As the `daily` version might provide an empty answer (the upstream daily build
|
||||
for today has not yet been released), there's an optional `-d` flag to
|
||||
ascertain a `daily` query would reply with a valid answer, pointing out to the
|
||||
last (current) daily release available (same as `current`):
|
||||
If the daily version has not been built today (e.g. likely between
|
||||
midnight and 03:00 CET), a `daily` query will result in a blank output.
|
||||
|
||||
To avoid this, the option `-d` will modify the query as "today's build or the
|
||||
most recent one" (the most recent one being the "current" one - as it would
|
||||
have been called with `current` query instead of `daily`):
|
||||
|
||||
loaih getversion daily -d
|
||||
|
||||
## Multiple query ##
|
||||
## Multiple queries ##
|
||||
|
||||
It is possible to ask for different queries in the same call, by separating
|
||||
It is possible to ask for different queries in the same run, by separating
|
||||
each query with a *comma* ',':
|
||||
|
||||
loaih getversion 7.4,fresh,still
|
||||
|
||||
This asks `loaih` to resolve to the latest version of the 7.4 branch, to
|
||||
the actual "fresh" stable release, and to the actual "still" release. All
|
||||
results should be reported to standard output in the order requested.
|
||||
|
||||
## JSON output ##
|
||||
|
||||
The information normally given on the standard output can be also provided as
|
||||
|
|
|
|||
Loading…
Reference in New Issue