summaryrefslogtreecommitdiff
path: root/.gitlab-ci.yml
diff options
context:
space:
mode:
authorSimon McVittie <smcv@collabora.com>2022-06-27 12:41:41 +0100
committerSimon McVittie <smcv@collabora.com>2022-07-13 20:36:13 +0100
commit5eee2d552a27688a1ff33e3a587f45e6406c85cf (patch)
tree4a7b4e71b5f98374f74f59373ea677572d54aa6d /.gitlab-ci.yml
parent600926adce7ecc7d93af323749c7d02621f0cf08 (diff)
downloaddbus-5eee2d552a27688a1ff33e3a587f45e6406c85cf.tar.gz
CI: Verify that Autotools `make dist` includes everything needed for Meson
This is similar to what we have done for CMake since dbus/dbus!87 (commit 1063bba "CI: Do the CMake native debug build from an Autotools `make dist`"). Our official source releases are Autotools `make dist` tarballs, so our CI should assert that such tarballs contain everything necessary to do a CMake or Meson build, so that downstream distributions using our tarballs as source can choose their preferred build system. When the Meson build system is ready to be recommended as more preferred than Autotools, we can do as GLib did: stop releasing `make dist` tarballs, and start releasing `meson dist` tarballs instead (which will change nothing for Meson or CMake users, but Autotools users will have to run autoreconf or autogen.sh before building). Signed-off-by: Simon McVittie <smcv@collabora.com>
Diffstat (limited to '.gitlab-ci.yml')
-rw-r--r--.gitlab-ci.yml2
1 files changed, 2 insertions, 0 deletions
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index e973fd70..81ccc6f1 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -181,6 +181,8 @@ debian meson:
extends:
- .meson-common
- .debian-build
+ variables:
+ ci_buildsys: "meson-dist"
debian mingw32 autotools debug:
extends: .debian-build