GNOME Bugzilla – Bug 751492
Update bootstrap moduleset
Last modified: 2015-07-06 08:57:02 UTC
Since we added m4-common and other useful stuff for general purpose use of the bootstrap moduleset, we should probably avoid installing stuff that is wildly out of date, or that fails the minimum requirements.
Created attachment 306087 [details] [review] bootstrap: Update gettext We need support for various formats, like desktop files, gsettings schemas, and GtkBuilder XML.
Created attachment 306088 [details] [review] bootstrap: Update the version of automake We depend on 1.14, now.
Created attachment 306089 [details] [review] bootstrap: Bump m4 Latest stable release, from 2013.
Created attachment 306090 [details] [review] bootstrap: Bump up to autoconf 2.69 Latest stable release, from 2012.
Created attachment 306091 [details] [review] bootstrap: Bump up to Python 2.7.10 Latest stable release for the maintenance branch.
Created attachment 306092 [details] [review] bootstrap: Bump up pixman to 0.32.6 Released in 2014.
Review of attachment 306089 [details] [review]: ::: modulesets/bootstrap.modules @@ +46,3 @@ <autotools id="m4" autogen-sh="configure"> <branch repo="ftp.gnu.org" + module="m4/m4-1.4.17.tar.bz2" version="1.4.16" Version mismatch here: 1.4.16 versus 1.4.17.
Review of attachment 306088 [details] [review]: CentOS 7 only has automake 1.13.4; do we really want to depend on 1.14? What advantages does that bring us over 1.13? (1.13 itself is a quantum leap over 1.11.)
Could m4-common be moved to a regular moduleset? this will allow most users to totally ignore the bootstrap moduleset.
(In reply to David King from comment #7) > Review of attachment 306089 [details] [review] [review]: > > ::: modulesets/bootstrap.modules > @@ +46,3 @@ > <autotools id="m4" autogen-sh="configure"> > <branch repo="ftp.gnu.org" > + module="m4/m4-1.4.17.tar.bz2" version="1.4.16" > > Version mismatch here: 1.4.16 versus 1.4.17. Fixed locally.
(In reply to Philip Withnall from comment #8) > Review of attachment 306088 [details] [review] [review]: > > CentOS 7 only has automake 1.13.4; do we really want to depend on 1.14? What > advantages does that bring us over 1.13? (1.13 itself is a quantum leap over > 1.11.) I originally bumped to 1.13.4, but then noticed that the IRC discussion that prompted this update included something depending on 1.14. Also: 12:03 < tpm> latest gstreamer depends on automake 1.14 now fwiw To be fair, if I were running CentOS, I'd go straight to bootstrap — it's as alien to continuous software development as MacOS.
(In reply to Frederic Peters from comment #9) > Could m4-common be moved to a regular moduleset? this will allow most users > to totally ignore the bootstrap moduleset. I'm struggling to find a place to add it to, though. Maybe gnome-suites-core-deps, or gnome-sysdeps; I'd still keep it in bootstrap, for non-Linux users that do not build GNOME and have to go through bootstrap anyway.
gnome-suites-core-deps would be fine, and just like it was the case for gnome-common modules depending on m4-common should declare the dependency.
(In reply to Frederic Peters from comment #13) > gnome-suites-core-deps would be fine, and just like it was the case for > gnome-common modules depending on m4-common should declare the dependency. Well, I guess the whole idea is to *not* to have to express the dependency, which will get boring fast. Pretty sure a bunch of components simply forgot to add it, and rely on the dependency graph to fix that for them.
(In reply to Philip Withnall from comment #8) > Review of attachment 306088 [details] [review] [review]: > > CentOS 7 only has automake 1.13.4; do we really want to depend on 1.14? What > advantages does that bring us over 1.13? (1.13 itself is a quantum leap over > 1.11.) Just checked, and m4-common depends on automake 1.14, so if we include m4-common anywhere we need to bump up the automake dependency. Alternatively, we need to relax the requirement in m4-common itself.
*** Bug 751491 has been marked as a duplicate of this bug. ***
*** Bug 750972 has been marked as a duplicate of this bug. ***
(In reply to Emmanuele Bassi (:ebassi) from comment #11) > (In reply to Philip Withnall from comment #8) > > Review of attachment 306088 [details] [review] [review] [review]: > > > > CentOS 7 only has automake 1.13.4; do we really want to depend on 1.14? What > > advantages does that bring us over 1.13? (1.13 itself is a quantum leap over > > 1.11.) > > I originally bumped to 1.13.4, but then noticed that the IRC discussion that > prompted this update included something depending on 1.14. > > Also: > > 12:03 < tpm> latest gstreamer depends on automake 1.14 now fwiw > > To be fair, if I were running CentOS, I'd go straight to bootstrap — it's as > alien to continuous software development as MacOS. In that case let’s just go with 1.14. Commit all the patches and let’s stop people tripping up over undefined macros ASAP.
Thanks, I've pushed all the patches to the bootstrap moduleset, since it's needed anyway. As for having the m4-common/autoconf-archive installed: I've added it to gnome-suites-core-deps, but I did not add it as a dependency. A simple hack would be to add it as a dependency of gnome-common, and then phase out gnome-common later on. For further discussion, I've filed bug 752009, so we can close this one.