From: Axel.Thimm@ATrpms.net (Axel Thimm)
To: lm-sensors@vger.kernel.org
Subject: Upcoming rpms: i2c headers under /usr/include/i2c
Date: Thu, 19 May 2005 06:25:28 +0000 [thread overview]
Message-ID: <20050101164046.GP28747@neu.nirvana> (raw)
In-Reply-To: <20041230173527.GF10397@neu.nirvana>
Hi,
On Sat, Jan 01, 2005 at 05:06:00PM +0100, Jean Delvare wrote:
> > packaging up i2c and lm_sensors I had to move the i2c headers
> > somehwere else than under /usr/include (and /usr/local is "forbidden"
> > for packages).
> >
> > Due to lack of any further creative thinking I just added another i2c
> > directory hierarchy, so the rpms will offer
> >
> > /usr/include/i2c/linux/i2c -> 2.9.0
> >
> > and glibc-kernheaders will contain the old i2c headers under
> >
> > /usr/include/linux/i2c
> >
> > Building lm_sensors against that is not an issue, as the location of
> > the headers can be specified. I wonder if there are other projects
> > depending on the i2c headers, that would have to be diverted to the
> > new location when packaged.
>
> I have no idea whether other packages need it. If there are, these would
> probably be third-party multimedia drivers.
>
> Please note that almost all headers included in lm_sensors are not
> supposed to be "exported" to /usr/include (or whatever) since they
> really are headers for kernel space, not user space.
Where should kernel space headers for building depending kernel
modules go? You need the "i2c-kernheaders" at least for building the
lm_sensors kernel modules. Perhaps /usr/include/linux is for userland
interfacing the kernel, but then there is no FHS place for
kernel-kernel headers (they are assumed to be hiding in the kernel
source only). Perhaps per kernel /lib/modules/.../{source,build}
locations would have been more appropriate.
> I have removed all header exports from i2c 2.9.0, and lm_sensors
> will probably go the same path soon. The ony file which is really
> needed from userspace is i2c-dev.h (the one which is in lm_sensors,
> but which should probably be moved back to i2c at some later time).
>
> > I also packaged the headers into i2c-kernheaders instead of
> > ivtv-devel, as this seems to be the current practice at Red Hat
> > (headers for conventional libs get into foo-devel, headers for kernel
> > modules get into foo-kernheaders).
>
> I assume you mean i2c-devel, not ivtv-devel?
Yes, sorry, a typo. :)
--
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20050101/f3bb3ac6/attachment.bin
next prev parent reply other threads:[~2005-05-19 6:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:25 Upcoming rpms: i2c headers under /usr/include/i2c Axel Thimm
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Axel Thimm
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Axel Thimm [this message]
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Axel Thimm
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=20050101164046.GP28747@neu.nirvana \
--to=axel.thimm@atrpms.net \
--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.