Fixed pages of the Wiki.
parent
95c44dab03
commit
d78d30cf2c
21
Build.md
21
Build.md
|
@ -13,7 +13,7 @@ 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 lowerst number of options to
|
||||
Hopefully, the chosen defaults would require the lowest number of options to
|
||||
be passed to the `build` command.
|
||||
|
||||
|
||||
|
@ -40,29 +40,30 @@ For the full description of all the available options and their relative default
|
|||
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**.
|
||||
v1.3.3, to the point this is indeed a **breaking change**.
|
||||
|
||||
|
||||
## Multiple single builds ##
|
||||
|
||||
Also the `build` verb supports multiple query:
|
||||
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`), 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).
|
||||
versions will overlap (e.g. `7.5,7.5.9.2`, both queries likely resulting in an
|
||||
AppImage filename 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` subfolder that will be created if missing and
|
||||
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).
|
||||
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.
|
||||
|
|
|
@ -5,7 +5,7 @@ The page describes how to install `loaih` to help build the AppImages.
|
|||
## From sources ##
|
||||
|
||||
You can build `loaih` from the sources in [this same
|
||||
site](/libreitalia/loaih/).
|
||||
site](https://git.libreitalia.org/libreitalia/loaih/).
|
||||
|
||||
1. Clone the repository:
|
||||
```
|
||||
|
@ -31,11 +31,12 @@ sudo python3 setup.py install
|
|||
## From Releases ##
|
||||
|
||||
When a new version is released, a binary artifact of the package will be
|
||||
uploaded to this website in the [Release](https://git.libreitalia.org/libreitalia/loiah/releases)
|
||||
uploaded to this website in the [Release](https://git.libreitalia.org/libreitalia/loaih/releases)
|
||||
section.
|
||||
|
||||
1. Find the latest relaease in the [Release](https://git.libreitalia.org/libreitalia/loaih/releases)
|
||||
page and download the relative `.whl` file (e.g. `loaih-1.3.3-py3-none-any.whl`);
|
||||
1. Find the latest relaease in the
|
||||
[Release](https://git.libreitalia.org/libreitalia/loaih/releases) page and
|
||||
download the relative `.whl` file (e.g. `loaih-1.3.3-py3-none-any.whl`);
|
||||
2. Ensure you have the `wheel` package installed in your system:
|
||||
```
|
||||
pip install wheel
|
||||
|
|
|
@ -1,16 +1,19 @@
|
|||
## Prerequisites ##
|
||||
# Prerequisites #
|
||||
|
||||
To build any LibreOffice AppImage, you need the following software already
|
||||
installed on your machine:
|
||||
|
||||
* `cp`: standard POSIX utility to copy files;
|
||||
* `dpkg`: Considering that we build the AppImage from the Debian packages,
|
||||
* `find`: it is used mostly to interact with downloaded files;
|
||||
* `fuse` and the relative kernel modules loaded;
|
||||
* `rsync`: if the repository is remote, the application can publish directly
|
||||
the contents using rsync;
|
||||
* `dpkg`: Considering that we build the AppImage from the Debian packages, we
|
||||
definitely need a way to extract the contents from .deb packages;
|
||||
* `find`: it is used mostly to interact with files inside the downloads and
|
||||
storage paths;
|
||||
* `fuse` needs to be installed and the relative kernel module needs to be
|
||||
loaded;
|
||||
* `rsync`: if the repository is remote, `loaih` can publish directly
|
||||
the contents using `rsync` and SSH;
|
||||
* `sed`: used to manipulate some source files;
|
||||
* `tar` and `gzip`: used to unpack the general downloads from LibreOffice
|
||||
* `tar` and `gzip`: used to extract the archives from LibreOffice
|
||||
official websites.
|
||||
|
||||
---
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
# Usage - versions #
|
||||
|
||||
`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` can be used to find out information about a specific LibreOffice version; 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` can be used as:
|
||||
|
||||
|
@ -39,7 +39,7 @@ number); for a working example, 20231231 for the December 31st, 2023.
|
|||
|
||||
## Fallback to current for missing daily versions ##
|
||||
|
||||
If the daily version has not been built today (e.g. likely between
|
||||
If the daily upstream 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
|
||||
|
|
Loading…
Reference in New Issue