From 33f14a700276a50f45dbac5d440c8e22e3c2d376 Mon Sep 17 00:00:00 2001 From: Matthias Clasen Date: Tue, 7 Jun 2016 15:20:20 -0400 Subject: [PATCH] Document /app/manifest.json This is a nice bit of reproducibility that we shouldn't leave undocumented. --- doc/flatpak-builder.xml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/doc/flatpak-builder.xml b/doc/flatpak-builder.xml index 9e397eb52..a8c54fb91 100644 --- a/doc/flatpak-builder.xml +++ b/doc/flatpak-builder.xml @@ -82,7 +82,10 @@ After this you will end up with a build of the application in DIRECTORY, which you can - export to a repository with the flatpak build-export command. + export to a repository with the flatpak build-export command. If you use the + option, flatpack-builder will do the export for you at the end of the build process. When flatpak-builder does the + export, it also stores the manifest that was used for the build in /app/manifest.json. The manifest is 'resolved', + i.e. git branch names are replaced by the actual commit IDs that were used in the build. At each of the above steps flatpak caches the result, and if you build the same file again, it will start