It is possible to get duplicated lines here, and we just want the first.

We should use https instead of git for our urls.

We want to default to online docs as they will be the most up to date.
If we don't have that, we'll load from docdir (or translate to the host
if we are accessing via flatpak).

We might need to find the path on the host, so add a helper to join paths
to get access to the file on the host.

These will get installed to $(docdir)/html which ends up being something
like /opt/gnome/share/doc/gnome-builder/html. We can use these to show
documentation locally without loading an internet site.

Additionally, we can use the doctree files if we want to navigate docs
locally within Builder.

Sort of annoying, but first tab stop is 3, then 4 after that for python.

If we are not advancing to or past IDE_BUILD_PHASE_BUILD, then there is no
need to clear the previous diagnostics.

https://bugzilla.gnome.org/show_bug.cgi?id=779526

This let's the listener know what stage we are advancing the pipeline to.

https://bugzilla.gnome.org/show_bug.cgi?id=779526

We can fallback to using various cflags/cxxflags from the build
environment.

We now rely on the help code that is going into doc/. We can just redirect
to builder.readthedocs.io until we statically generate docs and bundle
them.

We only want our appdata to show up in the final tree.

We don't really need this anymore, and it just wastes space. We should
instead make our build messages very clear as they come from the
particular build stages/phases.

This allows Builder flatpak to communicate with the packagekit daemon on
the host to install flatpak-builder.

If we are missing flatpak or flatpak-builder packages on the host, then
install them before installing runtimes. This is necessary so that we
can execute the flatpak-builder command to perform flatpak builds.