From: Alexander Smirnov <asmirnov@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: Building images without kernel
Date: Thu, 5 Apr 2018 12:54:02 +0300 [thread overview]
Message-ID: <f968e12e-66c8-211d-35bb-89a073fc33f4@ilbers.de> (raw)
In-Reply-To: <5a2e722a-9745-a759-a84b-8b11f445b71a@siemens.com>
On 04/05/2018 12:40 PM, Jan Kiszka wrote:
> On 2018-04-05 11:30, Claudius Heine wrote:
>> Hi,
>>
>> my use-case is creating nfs root file systems with isar, so I don't need
>> the kernel created by isar. That worked with older isar version.
>> Now we have a strong dependency to some kernel.
>>
>> Using my multiconfig it currently complains about:
>> Nothing PROVIDES 'linux-image-${KERNEL_NAME}'
>>
>> Sure I can just set `KERNEL_IMAGE` to something, but wouldn't that then
>> deploy the kernel to my rfs?
>
> That hard dependency is encoded into isar-image-base.bb (I think it was
> before as well). You could probably do IMAGE_INSTALL_remove, or you
> provide a linux-image-none recipe (KERNEL_NAME=none to install nothing
> in your image. Maybe we should include such a dummy recipe upstream so
> that this case can be handled without boilerplate code.
>
Another approach could be distro features, like it's done in Yocto via
DISTRO_FEATURES. The features could be: kernel, bootloader, debug etc...
In general I think it's eventually very useful cascading.
Alex
prev parent reply other threads:[~2018-04-05 9:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 9:30 Claudius Heine
2018-04-05 9:40 ` Jan Kiszka
2018-04-05 9:54 ` Alexander Smirnov [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=f968e12e-66c8-211d-35bb-89a073fc33f4@ilbers.de \
--to=asmirnov@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/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