Including on glib deprecation warnings, which are probably the only ones
we care about.

This assumes that XDT_FEATURE_DEBUG is used on all projects where
build_project.yml is included, which is currently the case.

This only applies to the build stage, as other distcheck-specific
warnings may appear that we don't necessarily want to turn into errors,
especially on vala projects. Also, this leaves open the possibility of
applying another debug level to distcheck, and thus compiling other code
paths.

By default, projects are configured so that a running pipeline is
interrupted if new changes are pushed in a merge request. But for this
to work in practice, all jobs in the pipeline must also be flagged
interruptible, otherwise the pipeline is not interrupted.

See https://docs.gitlab.com/ee/ci/yaml/index.html#workflowauto_cancelon_new_commit

Related: apps/orage#32

- More recent version of everything, should help to introduce new
  features.
- Bump docker dind (docker-in-docker) image used to build CI container
  itself

Probably a regression introduced in 2759f19c.

Fixes: #62

For xfce4-weather-plugin.

Related: panel-plugins/xfce4-weather-plugin!26

This is only useful for components packaged in flatpak in practice, i.e.
for Mousepad and Ristretto. There's no point in asking to update this
file if it's irrelevant.

Hopefully this will prevent releasing without changing the version
number.

For xfce4-indicator-plugin.

We use C99 features in various places (especially init-statement in for
loops), and C99 allows declaration after statement. This also avoids
warnings from other projects, like GObject Introspection >= 1.76.1 via
g-ir-scanner.

For gettext migration of project containing a policykit file.

Makes 'xfce-do-release' as well usable for xfwm4, which has some more
spaces in the line: 'm4_define([xfwm4_version_tag],   [git])'

MR !74

Jan Ziak authored 4 years ago and Romain Bouvier committed 2 years ago

This patch enables GLib deprecation warnings in all XFCE apps and libraries
containing function calls such as XDT_CHECK_PACKAGE([GLIB], [glib-2.0], [2.56.0])
in their configure.ac.in files in the following way:

AC_DEFINE(GLIB_VERSION_MAX_ALLOWED, GLIB_VERSION_2_56, Prevent post 2_56 APIs)
AC_DEFINE(GLIB_VERSION_MIN_REQUIRED, GLIB_VERSION_2_56, Ignore post 2_56 APIs)

The 3rd argument passed to XDT_CHECK_PACKAGE([GLIB], ...) selects the
GLib API version. So XDT_CHECK_PACKAGE([GLIB], [glib-2.0], [2.44.0])
would add:

AC_DEFINE(GLIB_VERSION_MAX_ALLOWED, GLIB_VERSION_2_44, Prevent post 2_44 APIs)
AC_DEFINE(GLIB_VERSION_MIN_REQUIRED, GLIB_VERSION_2_44, Ignore post 2_44 APIs)

The enabled warnings can be overridden by the app or library by using
the two AC_DEFINEs after calling XDT_CHECK_PACKAGE([GLIB], ...).

Something like XDT_CHECK_PACKAGE([GLIB], [glib-2.0], [2.45.8]) will make
the XFCE app or library uncompilable because 2.45 isn't a stable GLib release.

See also: apps/xfce4-notifyd#34



Signed-off-by: Jan Ziak <0xe2.0x9a.0x9b@xfce.org>

Akbarkhon Variskhanov authored 2 years ago and Gaël Bonithon committed 2 years ago

This avoids situations like `export EGREP=egrep; ./autogen.sh`