From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Suppress kernel image from the filesystem image
Date: Wed, 17 Jun 2009 20:06:30 -0400 [thread overview]
Message-ID: <20090618000630.GD21132@denix.org> (raw)
Hi,
When discussing the issue of suppressing the kernel image from the filesystem
image, it was suggested it is still an open question:
<Crofton|work> the kernel image getting installed in the image has been a long
standing headache
Several ways were mentioned, like fiddling with FILES variable and using
BAD_RECOMMENDATIONS. But the correct method is supposed to be overriding the
RDEPENDS_kernel-base from kernel.bbclass:
<pb___> denix0: these lines seem to suggest what the intended behaviour was:
<pb___> # Allow machines to override this dependency if kernel image files are
<pb___> # not wanted in images as standard
<pb___> RDEPENDS_kernel-base ?= "kernel-image"
<pb___> but, for reasons that are not entirely clear to me at the moment, my
efforts to override RDEPENDS_kernel-base did not meet with success.
I played with it for some time and realized that in order for it to work, the
kernel needs to be rebuilt before the new dependencies take place. So, I
added this to the local.conf:
RDEPENDS_kernel-base = ""
And after rebuilding the kernel and the filesystem I no longer see kernel
image in the filesystem!
The only problem I see with this approach is it builds the kernel packages
differently (USE-flags, anyone?) and if I use a public feed, I may end up
installing kernel image into the system again...
--
Denys
next reply other threads:[~2009-06-18 0:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 0:06 Denys Dmytriyenko [this message]
2009-06-18 11:01 ` Suppress kernel image from the filesystem image Phil Blundell
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=20090618000630.GD21132@denix.org \
--to=denis@denix.org \
--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