From: Alexander Smirnov <asmirnov@ilbers.de>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH 1/1] meta-isar/isar-image-base: make kernel optional
Date: Thu, 3 May 2018 19:30:09 +0300 [thread overview]
Message-ID: <c1020a03-76cc-7b6c-f57c-dd84682bcadf@ilbers.de> (raw)
In-Reply-To: <20180503182709.44044eeb@md1pvb1c.ad001.siemens.net>
On 05/03/2018 07:27 PM, Henning Schild wrote:
> Am Thu, 3 May 2018 19:18:42 +0300
> schrieb Alexander Smirnov <asmirnov@ilbers.de>:
>
>> On 05/03/2018 06:58 PM, Henning Schild wrote:
>>> Am Fri, 13 Apr 2018 12:38:20 +0200
>>> schrieb Baurzhan Ismagulov <ibr@radix50.net>:
>>>
>>>> On Thu, Apr 12, 2018 at 04:36:14PM +0200,
>>>> claudius.heine.ext@siemens.com wrote:
>>>>> diff --git a/meta-isar/recipes-core/images/isar-image-base.bb
>>>>> b/meta-isar/recipes-core/images/isar-image-base.bb index
>>>>> 6b0030b..d39a25e 100644 ---
>>>>> a/meta-isar/recipes-core/images/isar-image-base.bb +++
>>>>> b/meta-isar/recipes-core/images/isar-image-base.bb @@ -16,7 +16,7
>>>>> @@ PV = "1.0" inherit image
>>>>> inherit isar-bootstrap-helper
>>>>>
>>>>> -IMAGE_INSTALL += "linux-image-${KERNEL_NAME}"
>>>>> +IMAGE_INSTALL += "${@ ("linux-image-" + d.getVar("KERNEL_NAME",
>>>>> True)) if d.getVar("KERNEL_NAME", True) else ""}"
>>>>
>>>> If I want to generate an NFS rootfs w/o the kernel and an SD image
>>>> with one, how would I proceed? Do I understand correctly, the
>>>> latter recipe would list this line, and the former would not?
>>>
>>> I think the answer would be with two image recipes that
>>> inherit/override each other. So the main one that is probably
>>> derived from isar-image-base and would be called product-nfs.bb and
>>> product-wic.bb would overwrite some variables from the -nfs version.
>>>
>>> That patch should be merged, i already heard from someone else who
>>> now cherry-picked that into their fork.
>>
>> Started test build, will apply afterwards.
>>
>> But, I've looked at this patch again, and I think that this line
>> should go to image class instead of recipe, it's already generic
>> enough. Otherwise you have to copy this magic expression to every new
>> image recipe (if you not inherit isar-image-base).
>
> Ok, i just wanted to vote for the cause, not the implementation.
>
This patch will stay as it is, for sure :-)
Alex
next prev parent reply other threads:[~2018-05-03 16:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 14:36 [PATCH 0/1] Optional kernel claudius.heine.ext
2018-04-12 14:36 ` [PATCH 1/1] meta-isar/isar-image-base: make kernel optional claudius.heine.ext
2018-04-13 10:38 ` Baurzhan Ismagulov
2018-04-13 10:45 ` Claudius Heine
2018-04-13 11:23 ` Baurzhan Ismagulov
2018-04-16 7:03 ` Claudius Heine
2018-04-16 7:09 ` Jan Kiszka
2018-04-16 8:27 ` Claudius Heine
2018-05-03 15:58 ` Henning Schild
2018-05-03 16:18 ` Alexander Smirnov
2018-05-03 16:27 ` Henning Schild
2018-05-03 16:30 ` Alexander Smirnov [this message]
2018-05-03 18:50 ` Alexander Smirnov
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=c1020a03-76cc-7b6c-f57c-dd84682bcadf@ilbers.de \
--to=asmirnov@ilbers.de \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.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