GitLab

These don't map to our naming in Builder, so adjust them to match closer
to what we support in Builder.

If we create a plugin whose interface does not require IdeObject but
plugin inherits from IdeObject, ensure we set the context property.

Sometimes libtool wants stdin (doing things like <0) so we need to pass in
a valid stdin rather than /dev/null.

For the general purpose PHP extension case, where you're writing some C
or C++ code for an extension.

phpize is run to bootstrap the project, configure to configure, make to
build, make clean to clean and make install to install.

It looks for "config.m4" in the root of the project to determine that the
project is a phpize project.

This was missing from subprocess, and it can be very helpful when working
with subprocesses in Python to avoid converting things to GBytes.

To make it work, you need to have
python3-docutils installed

We cannot rely on g_network_monitor_get_available() being specific enough
to tell us if we can reach builder.readthedocs.io, so use the can-reach
async API instead.

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

We don't want to copy immutable items for distcheck.

Until we have proper discheck stuff working with plugins getting copied,
just work around things.

We only want to show recent gnome versions by default, so make this a
define so we can easily change it.

This was accidentally doing some of the widgetry work from a thread, so
use the GTask to defer the results back to the main thread for safe access
to GTK.

When we add a custom widget, we need to ensure that the group is shown
so that we don't get in a state where the group is always hidden, such
as if we do async preference loading.

The call to flatpak_installation_list_remote_refs_sync in add_runtimes
causes Builder's interface to freeze, so run it in a separate thread
from the main one.

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

Fix typo (missing "you" in "We will accept patches for documentionation no matter how get them to us".  Fix grammar in configuring git sentence.  Add link to GNOME wiki for git best practices for those who want to learn more.

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

In case the caller forgets to set priority, handle the NULL case
specifically.

By using the wait_check_async and wait_check_finish functions, we can
make sure to return an error for the task when make fails, so the user
sees "Failed" in the omnibar and right panel.

If we discover the build system from the manifest, we can provide a type
hint to the build system loader. This allows us to get the right build
system for flatpak (thus ensuring our configure opts are correct).

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

We might need to take the parent directory if we are discovering the build
system from the flatpak manifest.

This adds an IdeBuildSystemDiscovery interface so that we can try to
discover the preferred build system during project loading based on
external data, such as a json manifest from flatpak.

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

If we have an idea of what build system should be used, we can provide that
during creation so that we sort the build systems in an order that prefers
the hint'd build system.

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