TBD: handle untracked files, finding merge-base (big rabbit-hole), make sure
both staged and unstaged changes are handled

Instead of shipping our own post installation script, we should use the
one provided by the gnome module inside Meson. It's one less file we have
to care about, and the gnome module is integrated into Meson, which means
it'll do some of the heavy lifting for us.

Bilal Elmoussaoui authored Feb 03, 2022 and Christian Hergert committed Feb 04, 2022

The proc-macro feature in rust-analyzer is still experimental, although
without it the experience with code that uses proc macros is sub-optimal.

As gtk-rs apps (the most common use case for Builder/Rust) make heavy
use of macros so opt-in to that by default.

+ render magic pngs

Actually fixes GNOME/gnome-builder#1615

- maybe efficient, but a source of containt pain

Fixes GNOME/gnome-builder#1617

- provide symbolic assets for jhbuild, podman, flatpak, toolbx and host
  "containers"

Fixes GNOME/gnome-builder#1610

fixes GNOME/gnome-builder#1615

fixes GNOME/gnome-builder#1616

Other than the GtkBuilder template, it's identical with the GTK3
version except for the imported GTK version :-)

gjs added support for EcmaScript modules a while ago. We expect all
apps to move away from gjs' own custom imports system eventually,
so for new apps it makes most sense to use standard syntax from the
get-go.

Fixes #1611

Phaedrus Leeds authored Jan 27, 2022 and Christian Hergert committed Jan 27, 2022

I copied the line "g_variant_new ("a{sv}", 0);" into libportal and it
led to an error message:
Bail out!
GLib:ERROR:../glib/gvarianttypeinfo.c:164:g_variant_type_info_check:
assertion failed: (info->alignment == 0 || info->alignment == 1 ||
info->alignment == 3 || info->alignment == 7)

So I assume it's wrong here too. I also don't know why
G_VARIANT_TYPE_ARRAY is being used, seems like it should be
G_VARIANT_TYPE_VARDICT.

Use -Dwebkit=disabled to disable webkit support.

Fixes #1137

This should determine the correct storage location if this got
altered from the default locations.

If we have a style for these, we might as well use them.

This enables clang machinery to work in podman environments.

This makes things a bit brighter, more contrast, and better fitting in
with the style updates of the desktop.

Now that this has gotten some actual time spent on it, we can flip over
to what we'd be using on GTK 4 in the future.

From updates in GtkSourceView.