I modified xsensors-0.20.ebuild to include the ~amd64 flag, copied it to xsensors-0.45.ebuild, ran ebuild xsensors-0.45 digest then emerge /usr/local/portage/x11-misc/xsensors/xsensors-0.45.ebuild and it downloaded properly, built properly, installed properly, and ran on amd64. And if it'll do that on a dual opteron, it'll likely do that for your garden variety x86, too. xsensors-0.20.ebuild also compiled, installed, and ran fine under amd64 but 0.45 is much better. Reproducible: Always Steps to Reproduce: 1. cp /usr/portage/x11-misc/xsensors/xsensors-0.20.ebuild /usr/portage/x11-misc/xsensors/xsensors-0.45.ebuild 2. Add ~amd64 flag to the new ebuild 3. ebuild digest /usr/portage/x11-misc/xsensors/xsensors-0.45.ebuild 4. emerge /usr/portage/x11-misc/xsensors/xsensors-0.45.ebuild Actual Results: xsensors downloaded, compiled, installed, and ran fine under my dual opteron system.
Created attachment 28605 [details] My modified ebuild. All I did was add the ~amd64 flag and change the filename. Yay for uniformity.
x11-misc/xsensors-0.20 marked ~amd64 in CVS now. Thanks Tyler! Reassigning to desktop-misc for a version bump to version 0.45.
Can someone using 2.4.x kernel please test 0.46 (i2c needs 2.4, I use 2.6), also make sure to change DEPEND to =x11-libs/gtk+-2*
It's worth noting that 0.20 does not work correctly with Fahrenheit temperatures. It would be kind of nice to get the new one in that has this fixed.
0.46 is already in portage, and there are no more recent versions afaik fixed
