From: Anders Darander <anders@chargestorm.se>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Issue with RDEPENDS in module.bbclass for initramfs
Date: Tue, 25 Oct 2011 08:35:12 +0200 [thread overview]
Message-ID: <201110250835.14996.anders@chargestorm.se> (raw)
We have recently started investigating to make an even smaller build of
our local distro & machine. This smaller build should be run exclusively
from an initramfs, thus we have a need to reduće the size of the rootfs
as much as possible. (Especially as we'd still like some "bigger"
tools/pieces in the initramfs).
However, our first attempt to create a small image turned our to be
larger than expected. After a first investigation, it turns out that our
external kernel modules have an RDEPENDS on kernel-image (this is from
module.bbclass). As we're creating an initramfs-based rootfs, this is
obviously not desired... Locally removeing that RDEPENDS reduces the
image as expected...
I understand that in the general distro case, there is a need to be able
to express a dependency on a certain kernel version. However, I really
don't think that bringing in the kernel-image is a good idea, not an
general embedded platforms at least. (On the x86 this is usually not a
problem, as you almost always have the kernel as a part of the rootfs
anyway).
Could we come up with another way of expressing this dependency? That
would definitely be valuable for the small-ish embedded systems.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
next reply other threads:[~2011-10-25 6:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 6:35 Anders Darander [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-25 6:09 Issue with RDEPENDS in module.bbclass for initramfs Anders Darander
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=201110250835.14996.anders@chargestorm.se \
--to=anders@chargestorm.se \
--cc=openembedded-core@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