GNOME Bugzilla – Bug 661953
Modernize autotools configuration
Last modified: 2018-05-24 13:04:30 UTC
Created attachment 199165 [details] [review] Use upstream gettext Patches following
Created attachment 199166 [details] [review] Use autoreconf instead custom script
Doesn't upstream gettext finally have a way to handle multiple po/ directories properly?
(In reply to comment #2) > Doesn't upstream gettext finally have a way to handle multiple > po/ directories properly? yea, you have to modify a variable in po*/Makevars file. New patch attached.
Created attachment 199185 [details] [review] Use upstream gettext.v2
Very nice :) However it should use $(PACKAGE)-libgimp etc. Also, po-tags seems to miss. I also don't understand how Makefile.in.in is going to be copied to the other po-foo/ directories, maybe we need to cp them explicitly in autogen,sh? I also notice the Makevars has significantly less --keyword options than the existing Makefile.in.in, and shouldn't it use $(top_builddir) instead of ..?
Javier, can you have a look at those questions?
So, aynthing going to happen with these changes for 2.10?
I think we should look into both patches, but someone needs to find the time that the new way does everything the old stuff did.
Comment on attachment 199166 [details] [review] Use autoreconf instead custom script Based on recent comments.
Comment on attachment 199185 [details] [review] Use upstream gettext.v2 Based on recent comments.
Given that this drops e.g. LIBTOOL_WIN32_REQUIRED_VERSION=2.2, we seem to lose the ability to require different minimal versions of tools for specific platforms.
Shouldn't we push this to 3.0 milestone? Updating the build system is cool, but hardly a blocker and would clean out the list.
Pushing to 3.0 milestone. Of course feel free to provide an updated patch before we release 2.10. It may still make it.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/381.