[Initiatives.wiki] Update DevOps with Flatpak
- From: Jordan Petridis <jpetridis src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [Initiatives.wiki] Update DevOps with Flatpak
- Date: Tue, 24 Jul 2018 22:38:24 +0000 (UTC)
commit f716feecaafd85d16a290d80c881fe80962769c4
Author: Jordan Petridis <jordanpetridis protonmail com>
Date: Tue Jul 24 22:38:20 2018 +0000
Update DevOps with Flatpak
DevOps-with-Flatpak.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
---
diff --git a/DevOps-with-Flatpak.md b/DevOps-with-Flatpak.md
index 7a2a230..d24b32e 100644
--- a/DevOps-with-Flatpak.md
+++ b/DevOps-with-Flatpak.md
@@ -187,7 +187,7 @@ stop_review:
This almost does what we would want, but not quite. If you build this way it will always try to fetch your
modules from the source specified in the manifest, but we want to use our local checkout instead. This is
fine if you only build the `master` branch but MRs need to be able to change the source to their checkout.
-To achieve this we use the `--stop-at=module` argument which will build all of the dependancies up to your
module from the manifest. Then we take over and need to install the application ourselves. This is why your
config
+To achieve this we use the `--stop-at=module` argument which will build all of the dependencies up to your
module from the manifest. Then we take over and need to install the application ourselves. This is why your
config
s `MESON_ARGS` variable needs to be kept in sync with your module's config options in the manifest.
# Parallel installation
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]