Hello release team! Dave and I are planning to kill off gnome-common. The macros from it have been migrated to autoconf-archive[1], and gnome-autogen.sh is mostly irrelevant boilerplate which should be deleted or open-coded in people’s autogen.sh files in the first place. Is it OK if we do this, and eliminate the module from the modulesets? We were thinking about making a final release which contains gnome-autogen.sh unmodified, plus all the m4 macros defined as deprecated. After that, we would make a final commit which replaces gnome-autogen.sh with an unconditional error message directing people towards a wiki page for migration[2]. If they want to continue compiling against an older version of gnome-common, that’s fine, but master would be dead. How does that sound? Philip [1]: http://www.gnu.org/software/autoconf-archive/ [2]: https://wiki.gnome.org/Projects/GnomeCommon/Migration, which I am about to write
Attachment:
signature.asc
Description: This is a digitally signed message part