From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] lmsensors: Initial commit.
Date: Fri, 19 Oct 2012 11:39:50 +0200 [thread overview]
Message-ID: <k5r74s$r0$1@ger.gmane.org> (raw)
In-Reply-To: <1350565318-13026-2-git-send-email-ferlandm@sonatest.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 18-10-12 15:01, Marc Ferland schreef:
> The lmsensors project provides hardware health monitoring tools in the
> form of kernel drivers, a user-space library and some helper programs.
> This recipe provides all the different user-space tools offered by
> lmsensors in separete packages. Startup scripts and default configuration
> files are also made available through this commit.
>
> The packages consist of (description text from lmsensors documentation):
> * lmsensors-libsensors: The user-space sensors support library code. *
> lmsensors-sensors: A console tool to report sensor readings and set new
> sensor limits. * lmsensors-sensord: A daemon to watch sensor values and
> log problems. It includes RRD support. * lmsensors-fancontrol: Controls
> fanspeeds responding to changes on temperature sensors. Configuration
> through pwmconfig. * lmsensors-sensorsdetect: This program tries to
> detect the available SMBus adapters and the chips connected to them, as
> well as Super-I/O and misc chips. * lmsensors-sensorsconfconvert: Convert
> configuration files from lmsensorsv2 to lmsensorsv3. *
> lmsensors-pwmconfig: tests the pwm (pulse width modulation) outputs of
> sensors for their effect on the fans and helps to setup the configfile
> for fancontrol. * lmsensors-isatools: This program sets/gets the
> registers of ISA or Super-I/O chips.
>
> Signed-off-by: Marc Ferland <ferlandm@sonatest.com> ---
> +++ b/meta-oe/recipes-support/lm_sensors/lmsensors_3.3.2.bb @@ -0,0
> +1,150 @@ +SUMMARY = "lm_sensors" +DESCRIPTION = "Hardware health
> monitoring applications" +HOMEPAGE = "http://www.lm-sensors.org/"
> +LICENSE = "GPLv2+ & LGPLv2.1+" +LIC_FILES_CHKSUM =
> "file://COPYING;md5=751419260aa954499f7abaabaa882bbe \ +
> file://COPYING.LGPL;md5=4fbd65380cdd255951079008b364516c"
> +PR = "r0"
Drop that
> +DEPENDS = "sysfsutils virtual/libiconv bison-native flex-native
> rrdtool" +PROVIDES = "\ +${PN}-libsensors \ +${PN}-sensors \
> +${PN}-sensord \ +${PN}-fancontrol \ +${PN}-sensorsdetect \
> +${PN}-sensorsconfconvert \ +${PN}-pwmconfig \ +${PN}-isatools \
Anything listed in PACKAGES is already in (R)PROVIDES, so drop the above
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org
iD8DBQFQgR/mMkyGM64RGpERAvJBAJ9Cnla/rkwCvnpoBauHCsKAYm7unQCcClGt
BYGjJVKXS5k9Z2Jg0Gf1Dww=
=Rc3D
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-10-19 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 13:01 [meta-oe][PATCH] lmsensors: Initial commit (cover letter) Marc Ferland
2012-10-18 13:01 ` [meta-oe][PATCH] lmsensors: Initial commit Marc Ferland
2012-10-19 9:39 ` Koen Kooi [this message]
2012-10-19 9:52 ` Paul Eggleton
-- strict thread matches above, loose matches on Subject: below --
2012-10-19 15:15 [meta-oe][PATCH] lmsensors: Initial commit (cover letter) Marc Ferland
2012-10-19 15:15 ` [meta-oe][PATCH] lmsensors: Initial commit Marc Ferland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='k5r74s$r0$1@ger.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox