sys-apps/lm_sensors-progs-2.6.4.ebuild Hardware Sensors Monitoring by lm_sensors (just programs) Ok, I'm not sure if this is the right way to do this. But if everyone decides it is, this could change a few ebuilds. I really think that packages that include both applications and kernel modules should be split up. If someone needs the modules compiled statically (which I do on my servers), the applications should be able to be installed separately. Such was the case with lm_sensors. I created this lm_sensors_progs ebuild for that purpose. This is going probably going to need a kernel source ebuild with lm_sensors patched in at some point, and I have that, but I am not prepared to maintain a kernel source. Furthermore, some of the chipsets in lm_sensors do not compile statically yet (so far, I've been lucky).
Created attachment 5115 [details] lm_sensors-progs-2.6.4.ebuild
Created attachment 5162 [details] lm_sensors-progs-2.6.5.ebuild
I just did a version bump. Also, I forgot to mention that some packages already depend on lm_sensors, such as mondo. lm_sensors-progs does not satisfy this dependency. I found it necessary to: emerge inject sys-apps/lm_sensors-2.6.5 Is there a less sloppy way to accomplish this?
Do you have an ebuild for the modules separately? If so I will go ahead and create a virtual/sensors_modules which can be satisfied either by a kernel OR by the lm_sensors-modules and which will be depended on by lm_sensors (which will now be just your lm_sensors-progs ebuild) Thanks for doing this I've been trying to get the time to fixor it myself. Any chance of you figuring out how the heck to do alsa-driver as well? Thanks!
I like that way of doing things! I will be glad to help out. Give me some time, and I'll submit what you requested.
2.6.5 and 2.7.0 in cvs thx.
