From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: lmsensors - separating userspace and kernel patch
Date: Thu, 19 May 2005 06:24:23 +0000 [thread overview]
Message-ID: <20031104201314.2ea6af4b.khali@linux-fr.org> (raw)
> Do you have any plans for creating a 'sensor-utils' package with just
> the user-space tools for lm-sensors?
>
> Would be nice and less confusing for 2.6 users....
First, we don't build packages. That task is left to, well... packagers.
And packagers are free to split our lm_sensors2 module in as many
packages as they want.
Second, userspace tools aren't ready for 2.6 yet anyway, although some
work has already been done to achive that.
Third, you can use "make user" and "make user_install" in lm_sensors2 to
build and install only the user-space tools.
That said, I agree that splitting our CVS module as a kernel module and
a user-space module would be great. But it is also a complex operation,
breaking developer's habits, making tracking changes harder, and so on.
For this reason, I doubt it'll be done soon, if ever. Maybe once there
is real user-space support for 2.6 kernels, we'll think of splitting,
who knows.
--
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/
reply other threads:[~2005-05-19 6:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20031104201314.2ea6af4b.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.