From: Jan Kiszka <jan.kiszka@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH 5/5] api: Rename IMAGE_TYPE to IMAGE_FSTYPES
Date: Tue, 14 Sep 2021 09:39:02 +0200 [thread overview]
Message-ID: <b9f29cb0-0960-3714-4b97-0904f46d89f9@siemens.com> (raw)
In-Reply-To: <4625067.OV4Wx5bFTl@home>
On 14.09.21 09:08, Uladzimir Bely wrote:
> In the email from понедельник, 13 сентября 2021 г. 21:27:47 +03 user Jan
> Kiszka wrote:
>> On 13.09.21 16:58, Uladzimir Bely wrote:
>>> The variable is renamed to get closer to OpenEmbedded/Poky
>>> variables naming. If user still uses IMAGE_TYPE, it will be used
>>> with the deprecation warning shown.
>>
>> IMAGE_FSTYPES [1] != IMAGE_TYPES [2].
>>
>> Jan
>>
>> [1]
>> https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#var-IMAG
>> E_FSTYPES [2]
>> https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#var-IMAG
>> E_TYPES
>
> Yes, in OE there are two variables:
> IMAGE_TYPES - full list of supported image types
> IMAGE_FSTYPES - image types to build
>
This is wrong, read the above manual again.
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2021-09-14 7:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 14:58 [PATCH 0/5] Support multiple image types in one build Uladzimir Bely
2021-09-13 14:58 ` [PATCH 1/5] image: Make WORKDIR and STAMPs unrelated to IMAGE_TYPE Uladzimir Bely
2021-09-13 14:58 ` [PATCH 2/5] wic-img: Set weak default value for WKS_FILE Uladzimir Bely
2021-09-13 14:58 ` [PATCH 3/5] start_vm: Use the first image type to start VM Uladzimir Bely
2021-09-13 14:58 ` [PATCH 4/5] meta-isar: Rework mc:qemuamd64-buster configs Uladzimir Bely
2021-09-13 14:58 ` [PATCH 5/5] api: Rename IMAGE_TYPE to IMAGE_FSTYPES Uladzimir Bely
2021-09-13 18:27 ` Jan Kiszka
2021-09-14 7:08 ` Uladzimir Bely
2021-09-14 7:39 ` Jan Kiszka [this message]
2021-09-14 7:50 ` Jan Kiszka
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=b9f29cb0-0960-3714-4b97-0904f46d89f9@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=ubely@ilbers.de \
/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