From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Ebuilds referencing /usr/src/linux makes baby Jesus kill kittens
Date: Fri, 23 Jul 2004 20:42:54 -0400 [thread overview]
Message-ID: <200407232042.54805.vapier@gentoo.org> (raw)
In-Reply-To: <20040723232250.6a3dbe33@snowdrop.home>
On Friday 23 July 2004 06:22 pm, Ciaran McCreesh wrote:
> Just a friendly reminder that you should really avoid messing around
> with /usr/src/linux inside ebuilds. In particular, code like the
> following is utterly wrong:
>
> if [ ! -e "/usr/src/linux/include/linux/dm-ioctl.h" ] ; then
the only packages that should poke around /usr/src/linux/ are kernel module
packages ... and like donnie said, using ${ROOT}/usr/src/linux/ is ok
> You shouldn't be using /usr/src/linux for headers either. I suggest
> people give the following a good read before they commit even more
> broken code to the tree:
agreed, headers should be taken from the system
-mike
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2004-07-24 0:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 22:22 [gentoo-dev] Ebuilds referencing /usr/src/linux makes baby Jesus kill kittens Ciaran McCreesh
2004-07-23 22:52 ` Donnie Berkholz
2004-07-24 0:42 ` Mike Frysinger [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=200407232042.54805.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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