_LATEST_AUTOMAKE should include automake 1.14 so that automake 1.14 is actually used by ebuilds using default WANT_AUTOMAKE="latest". --- autotools.eclass +++ autotools.eclass @@ -46,7 +46,7 @@ # Do NOT change this variable in your ebuilds! # If you want to force a newer minor version, you can specify the correct # WANT value by using a colon: <PV>:<WANT_AUTOMAKE> -_LATEST_AUTOMAKE=( 1.12:1.12 1.13:1.13 ) +_LATEST_AUTOMAKE=( 1.12:1.12 1.13:1.13 1.14:1.14 ) _automake_atom="sys-devel/automake" _autoconf_atom="sys-devel/autoconf"
i specifically did not do that yet. we want 1.14 to get used randomly at first and see feedback before we start (possibly) breaking all of ~arch.
Can we have a workaround to pull the previous automake if the latest one is not in _LATEST_AUTOMAKE ? for example, this breaks the build on a new mips system where only automake-1.14 is installed.
Now it should be appropriate time to update _LATEST_AUTOMAKE. I have been using patch from comment #0 for over 3 months without any problems.
*** Bug 482908 has been marked as a duplicate of this bug. ***
automake-1.14 has been out for a good amount of time, so let's start bugging people with it http://sources.gentoo.org/eclass/autotools.eclass?r1=1.156&r2=1.157
