On Wed, 2024-07-10 at 10:53 +0200, Marcus Folkesson via lists.openembedded.org 
wrote:
> The image-bootfiles class is used to put all files listed in
> IMAGE_BOOT_FILES into the root filesystem.
> 
> IMAGE_BOOT_FILES is used by the bootimg-partition wic plugin to put the
> files into a boot partition. 
> Be able to list files as "boot files" in e.g. your .conf or image files
> instead of install those in every recipe is a good thing.
> 
> It is not always desired to have a separate boot partition for boot
> files. Sometimes it could be good to have them as a part of the root
> filesystem.
> 
> For example, if a double copy strategy is used for update the system,
> then you probably want to update both the boot files and root filesystem
> at the same time as there may be dependencies.
> 
> v2:
>     - Removed the documentation from the patch series (will be submitted 
> later)
>     - Break out the parts in bootimg-partition that is used by
>       image-bootfiles to a common library
>     - Make the destination directory in root filesystem configurable
> v3:
>     - See changelog in patches
> 
> v4:
>     - See changelog in patches
> 
> v5:
>     - See changelog in patches
> 
> v6:
>     - See changelog in patches
> 
> Marcus Folkesson (2):
>   bootimg-partition: break out code to a common library.
>   image-bootfiles.bbclass: new class, copy boot files to root filesystem

During review we've been in two minds about these changes. It is a
fairly specific use case. In general if you wanted these files in the
rootfs, you'd never have set the variable in the first place. Setting
the variable, then using a class to put them back where they were
originally seems a strange thing to want to do and I'm not sure we want
core support for it.

That said, I understand how someone can get into that situation.

We have therefore merged the first patch which allows a standalone
class but we don't really want to take the class itself. This is partly
also partly as there wouldn't usage/testing in core.

If there becomes a large number of users of it over time, we can
reconsider that decision but right now, I don't think it make sense.

Cheers,

Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#202335): 
https://lists.openembedded.org/g/openembedded-core/message/202335
Mute This Topic: https://lists.openembedded.org/mt/107138981/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to