marko10_000
/
flatpak-builder
forked from Mirrors/flatpak-builder
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Document /app/manifest.json 

This is a nice bit of reproducibility that we shouldn't leave
undocumented.
tingping/wmclass
Matthias Clasen 2016-06-07 15:20:20 -04:00
parent 3639601848
commit 33f14a7002
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/flatpak-builder.xml
View File

@ -82,7 +82,10 @@
</itemizedlist>
After this you will end up with a build of the application in <arg choice="plain">DIRECTORY</arg>, which you can
export to a repository with the <command>flatpak build-export</command> command.
export to a repository with the <command>flatpak build-export</command> command. If you use the <option>--repo</option>
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.
</para>
<para>
At each of the above steps flatpak caches the result, and if you build the same file again, it will start