There is a more recent microcode update on urbanmyth.org than the latest in portage. As there is no public ChangeLog from Intel, according to urbanmyth.org, I have no way to determine the exact advantages of doing an upgrade - nevertheless the people at Intel probably have their reasons to do a new release.
Created attachment 41959 [details, diff] microcode-ctl-1.08-1.09.ebuild.patch Here is a patch to the sys-apps/microcode-ctl-1.08.ebuild that is needed before doing a version bumb. The only change from 1.08 is the microcode within the archive, but because the filname have changed a minimal patch to the ebuild is required.
Created attachment 41961 [details, diff] alternative patch As a second thought, there might be tempting to replace the date part of the microcode filename with an *. This will make version bumps easier (cp to new version, make a digest AND check that the new ebuild grabs the new microcode.) The last part will be important with either ebuild, as it is easy to miss that /etc/microcode.dat is missing if you are doing an upgrade.
added the -*.txt version to cvs, thanks :)
