lm-sensors update for 2.6.5+ kernels
Created attachment 28791 [details] lm-sensors-2.8.6.ebuild
What is the reason for: KEYWORDS="~amd64 -ppc -sparc -x86" ?
in portage
sorry for not answering earlier. the reason for the masking on other archs is that until recently, the lm-sensors for 2.6 kernels was masked in package.mask. however, the entry in package.mask prevented installation on amd64, where 2.6 is the only stable kernel... so it was removed and the mask was moved to KEYWORDS to prevent archs that use a 2.4 kernel from accidentally installing it. I'm guessing that the KEYWORDS should just be "~amd64" and not "~amd64 -ppc -sparc -x86", as the package isn't really broken for these archs if you're using a 2.6 kernel... just if you're using 2.4. *shrug*
don't you (developers) think, that it's time to move 2.6 kernels from development-sources, to some 'normal' location like vanilla-sources? it could be marked as ~x86 and newest lm-sensers could then change their keywords to the same. 2.6* kernels are stable and really popular those days...
Somebody please remove the darned -x86 keyword from the ebuild. 2.6.x has been out for a long time now and I'm tired of having to edit ebuilds by hand to get things to install instead of hanging up updates. This ebuild is opposite the reason for this bug. The reason this bug was filed was "lm-sensors update for 2.6.5+ kernels" When you submit ebuilds, _please_ submit working ebuilds, not ebuilds that unuseful.
mkdir -p /etc/portage echo sys-apps/lm-sensors -x86 >> /etc/portage/package.keywords emerge lm-sensors
How about fixing the ebuild instead of hiding the problem? I don't need or want a fix for every little package out there just because I'm running modern software. I apologize for venting, but the ease of upgrading to current packages and using modern packages was the whole reason why I chose gentoo. If I wanted to be stuck in software a year or two old, I'd have picked some other dinosaur distribution. Let me ask this. Is there a particular reason why lm-sensors is intentionally completely disabled? Not even ~x86, but -x86? Why even check in an ebuild if it's disabled.
it's marked as installable on amd64 because we dont support the 2.4 kernel at all on amd64. my understand of the issue is that marking it as testing or stable would break lm-sensors for anyone using a 2.4 kernel. i wouldnt know... like i said, 2.4 isnt even supported on my arch. read comment #4. perhaps you should instead be complaining that development-sources is still called development-sources, in which case you should be filing an entirely new bug.
