From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: RPM spec file patches for i2c and lm_sensors 2.8.1
Date: Thu, 19 May 2005 06:24:23 +0000 [thread overview]
Message-ID: <20031101120304.4807d0d6.khali@linux-fr.org> (raw)
In-Reply-To: <9D8C1A43309BAD4A9B46071DAF911D9E13FDA5@exch01.paracel.com>
> The kernel rpms for Fedora Core 1 (labeled as rawhide in the repo)
> already have 2.8.1 support. Userland lm_sensors needs to be updated,
> and I wanted to try building the kernel modules there also (otherwise
> one may miss a few).
True.
> If I make lm_sensors.spec a specfile for kernel modules it will
> probably become unreadable. Any help in packaging is appreciated!
Why would it become unreadable? Modules aren't that different from other
files. They are built the same way, installed the same way. I don't
really see the problem (but this is a long time since I last packaged
files in a RPM, so I might be missing something obvious).
Since lm_sensors' modules don't require patching the kernel source tree,
I sure would build them out of it and propose them as a separate
package. That way you got them all (which isn't the case when patching
the kernel tree) and it's less complicated to update the RPM file IMHO.
> BTW does lm_sensors 2.8.1 (userland & kernel modules) require i2c
> 2.8.1 or is i2c 2.8.0 already adequate? If the latter is true it would
> save me from rebuilding the RH7.3-RH9 kernels.
It requires i2c 2.8.1, because a unified delay function has been
introduced to replace the various separate ones that existed in 2.8.0.
--
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/
prev parent reply other threads:[~2005-05-19 6:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:24 RPM spec file patches for i2c and lm_sensors 2.8.1 Marc Rieffel
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Marc Rieffel
2005-05-19 6:24 ` Axel Thimm
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare [this message]
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=20031101120304.4807d0d6.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=lm-sensors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.