To avoid the complexities of passing (and chaining) OstreeAsyncProgress
objects around, we only create one just before calling to ostree.
The rest of flatpak only ever uses the new FlatpakProgress object.
Co-authored by: Philip Chimento <philip@endlessm.com>
Add a rule to generate a single-file html version of the
libflatpak api reference, for integration into readthedocs.
This is pretty plain, but serves the purpose.
Closes: #2526
Approved by: matthiasclasen
Avoid the 3-second 'afterlife' of instances by using
kill (pid, 0) instead of checking the file lock. We
trade pid for lock races, but this seems more reliable.
Also add flatpak_installation_launch_full that returns
a FlatpakInstance for the launched app, and lets us
avoid races around killing the app, by using a child
watch.
Closes: #2221
Approved by: matthiasclasen
We know the documentation is incomplete, so there seems little value
in having 'make check' tell us that. Everything except the documentation
check is expected to succeed, so it's now more useful to report test
failures in continuous integration systems, making functional
regressions more visible.
Signed-off-by: Simon McVittie <smcv@debian.org>
We need to explicitly tell gtk-doc about the XDG_APP_EXTERN macro,
otherwise it will ignore all of the function definitions.
Full docs are now produced. There are plenty of warnings which can be
fixed later.
