This appears to be an upstream bug: running "./configure --enable-cpufreq" and "./configure --disable-cpufreq" both disable the cpufreq applet, it is enabled only when the enable/disable switch is not present. gnome-applets-2.32.1.1-r1.ebuild uses use_enable cpufreq, thus disabling the cpufreq applet regardless of the value of the USE flag cpufreq. Reproducible: Always
Attach build.log, I am sure it worked in the past
Created attachment 327506 [details] build log
+*gnome-applets-2.32.1.1-r2 (27 Oct 2012) + + 27 Oct 2012; Pacho Ramos <pacho@gentoo.org> +gnome-applets-2.32.1.1-r2.ebuild: + configure is broken and hiddenly disables cpufreq always, bug #439768 by Juha + Aatrokoski. +
Actually, I think autoconf is fine, and it's a problem with the way the configure script from upstream is using the enable/disable macro. See bug #390877 for details and a patch. Cheers, James