Hi,

Things are looking pretty well with meson in GLib master. We have CI
working for pretty much all interesting platforms (more to come) and
there are only a few remaining issues with "Meson" tag in gitlab[1].

I think the longer we keep 2 build systems, the more time we waste on
useless tasks. So I would like to discuss a roadmap that would lead to
dropping autotools.

My proposal would be:
1) Starting from 2.57.2 (next dev release), create release tarballs
using "ninja dist" and recommend disto to build with Meson 0.46.1. This
would mean that './configure' in a release tarball won't work, people
still wanting to use autotools will have to update their scripts to use
"./autogen.sh" instead and adjust their build deps. IMHO, forcing a
small change is a good incentive to have most of our users switch to
meson. This would give us good feedback while still keeping the door
open to rollback if any blocker bug appears.
2) Starting from 2.59.1 (next dev cycle), drop autotools completely
from our git repository.	

Disclaimer: I'm not a GLib maintainer so this email is only about
opening the discussion. There is no decision made yet.

Opinions?

Regards,
Xavier Claessens.

[1] https://gitlab.gnome.org/GNOME/glib/issues?scope=all&utf8=%E2%9C%93
&state=opened&label_name[]=Meson
_______________________________________________
gtk-devel-list mailing list
gtk-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-devel-list