[OE-core] any value in keeping INITRAMFS_TASK?

[Andrea Adami]

On Thu, Feb 26, 2015 at 9:59 PM, Robert P. J. Day <rpjday at crashcourse.ca> wrote:
>
>   just tripped over INITRAMFS_TASK in kernel.bbclass, which claims to
> be only for backward compatibility and should be replaced by
> INITRAMFS_IMAGE:
>
>     # NOTE: setting INITRAMFS_TASK is for backward compatibility
>     #       The preferred method is to set INITRAMFS_IMAGE, because
>     #       this INITRAMFS_TASK has circular dependency problems
>     #       if the initramfs requires kernel modules
>
> but i still see usage over in
> meta-openembedded/meta-initramfs/recipes-kernel/linux/linux-yocto-tiny-kexecboot_3.1[07].bb:
>
> INITRAMFS_IMAGE = "initramfs-kexecboot-klibc-image"
> INITRAMFS_TASK = "${INITRAMFS_IMAGE}:do_rootfs"
>
> should that be updated, and INITRAMFS_TASK tossed?
>
> rday
>
> --
>
> ========================================================================
> Robert P. J. Day                                 Ottawa, Ontario, CANADA
>                         http://crashcourse.ca
>
> Twitter:                                       http://twitter.com/rpjday
> LinkedIn:                               http://ca.linkedin.com/in/rpjday
> ========================================================================
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core


Robert,

this is is an unobvious way to allow the build in one pass of:
- a standard kernel (without initramfs)
- a second kernel embedding an initramfs

The 'preferred method' does inject the initramfs in any recipe using
kernel.bbclass so to keep the old behavior (selectively add the
initramfs) we can circumvent it using INITRAMFS_TASK.

So no, please, don't toss it ;)

Cheers

Andrea