This patch adds a newline between the two warnings on the Persistent
workspace section. Without the newline the two warnings are shown as a
single one making it difficult to read.

Signed-off-by: Peter Senna Tschudin <peter.senna@collabora.com>

If the developer make changes to the new sdk before adding the
persistent disk, these changes will likely be overwritten by the
persistent disk. This patch adds a warning about this and points to the
README section that show where the old files are accessible.

Signed-off-by: Peter Senna Tschudin <peter.senna@collabora.com>

The document was not mentioning the availability of the toolchain for
two architectures and the URL on the wget command was incomplete. This
patch fixes these issues and also fixes typos.

Signed-off-by: Peter Senna Tschudin <peter.senna@collabora.com>

Frédéric Dalleau authored 5 years ago and Emanuele Aina committed 5 years ago

It is not clear through the link that they point to actual usage
documentation

Signed-off-by: Frédéric Dalleau <frederic.dalleau@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Point users to where sysroot and devroot tarballs are hosted.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

The cross-build-toolchain document already has instructions on using the
sysroot without relying on `ade` from non-Apertis hosts: link to it explicitly.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Frédéric Dalleau authored 5 years ago and Emanuele Aina committed 5 years ago

The cross build toolchain looks simple but it's usage is complex.
Add a documentation that shows how to use it.

Signed-off-by: Frédéric Dalleau <frederic.dalleau@collabora.com>

Signed-off-by: Ritesh Raj Sarraf <rrs@debian.org>

Having psdk on older SDKs may be useful. This patch adds pointers on
how to install psdk from the Debian package and from source code.

It also fixes a typo: initialing -> initializing

Signed-off-by: Peter Senna Tschudin <peter.senna@collabora.com>

This patch adds instructions to sdk-usage.md for guiding the user on how
to use the persistent disk on the SDK.

Signed-off-by: Peter Senna Tschudin <peter.senna@collabora.com>

Describe how sysroots and devroots work, what is their purposes, how are they
meant to be used and when.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Builds with the new, Buster-based Docker containers currently fail:
    --latex-engine has been removed.  Use --pdf-engine instead.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Clutter has been dead upstream for a long time. Point people to mature,
supported toolkits.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

The clutterized WebKit API has been dropped, focusing on the upstream
WebKit2GTK API, see https://phabricator.apertis.org/T5615



Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

https://phabricator.apertis.org/T3748



Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

The dist/ folder and the apertis hotdoc extension contained there are not being
used nowadays and their purpose is lost in time.

Given that nobody complained, let's remove them to reduce the amount of cruft
we carry.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Force a light background on images in the document. Transparent images
assume a light background and they work badly on the current dark one.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Move the devroot headings one level up so they don't end up under the
"Clang static analyzer" section.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Since we do not currently have an app store, this document may be
confusing to the users.

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Ritesh Raj Sarraf <rrs@debian.org>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Using `--no-perms` alone yielded surprising results, such as
directories with no execute bit set, which could thus not be accessed
by the web server.

One option would be to use `--no-perms --chmod=ugo=rwX` as suggested by
the `rsync` man page:

> In summary: to give destination files (both old and new) the source
> permissions, use --perms.  To give new files the destination-default
> permissions (while leaving existing files unchanged), make sure that
> the --perms option is off and use --chmod=ugo=rwX (which ensures that
> all non-masked bits get enabled)

This would mean that existing files would preserve their permissions.
But we don't actually care about preserving them, to the contrary we may
prefer forcing them to a known state such that redeploying from scratch
would give the same results.

In order to achieve this, set `--chmod=ugo=rwX` in combination with
`--perms` (implied by `-a`).

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Andre Moreira Magalhaes (andrunko) <andre.magalhaes@collabora.co.uk>

Sjoerd Simons authored 6 years ago and Emanuele Aina committed 6 years ago

First testing if a directory exists and then creating it is inherently
racy. Instead always try to create the directory and ignore the error if
it already existed.

Fixes build failures when doing parallel pdf builds

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>

At the moment only the master branch is uploaded to latest/ using the
`branch` conditional (which is only supported on multibranch pipelines).

What we really want is to:
* upload every branch to the appropriate release folder (e.g. 18.06/)
* ensure that latest/ is a symlink pointing to the release coming from
  the master branch

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Use the documentation builder Docker image matching the current release.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>