[jethro] Backport proposal

[jethro] Backport proposal

[Otavio Salvador]

Hello folks,

[Cced Robert Yang]

I would like to propuse the backport of following changes:

Author: Mariano Lopez <mariano.lopez@linux.intel.com>
Date:   Wed Dec 30 06:52:54 2015 +0000

    image_types.bbclass: Rebuild when WICVARS change

    The procces to do a wic image is to save a file with
    variables required by wic and then call wic using this
    file. Because this is external to bitbake if the vars
    change, the image won't be rebuild; an example of such
    is IMAGE_BOOT_FILES.

    This patch adds these variables to vardeps of do_rootfs
    when a wic image is build. This will rebuild the image
    if a variable needed by wic changes.

    [YOCTO #8693]

    Signed-off-by: Mariano Lopez <mariano.lopez@linux.intel.com>
    Signed-off-by: Ross Burton <ross.burton@intel.com>
    (cherry picked from commit 12c54d50ed4c321dc272beb3c6cb770965c979f1)

Author: Christopher Larson <chris_larson@mentor.com>
Date:   Tue Nov 10 14:18:20 2015 -0700

    image_types: improve wks path specification

    Hardcoding a full input path with zero flexibility goes against
everything the
    Yocto Project is about. Rework it to let the user specify the wks base
    filename with WKS_FILE and it'll search the layers for the wks file and use
    it.

    Signed-off-by: Christopher Larson <chris_larson@mentor.com>
    Signed-off-by: Ross Burton <ross.burton@intel.com>
    (cherry picked from commit 8cc7f5229f5447c2183ac319dd52c7ed737ec89b)

Those improve the 'wic' image support on Jethro and are merged into
master for a while. Could those be backported?

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: [jethro] Backport proposal

[akuster808]

On 2/24/16 11:50 AM, Otavio Salvador wrote:
> Hello folks
>
> [Cced Robert Yang]
>
> I would like to propuse the backport of following changes:


Seems responsible to me.

- armin
>
> Author: Mariano Lopez <mariano.lopez@linux.intel.com>
> Date:   Wed Dec 30 06:52:54 2015 +0000
>
>     image_types.bbclass: Rebuild when WICVARS change
>
>     The procces to do a wic image is to save a file with
>     variables required by wic and then call wic using this
>     file. Because this is external to bitbake if the vars
>     change, the image won't be rebuild; an example of such
>     is IMAGE_BOOT_FILES.
>
>     This patch adds these variables to vardeps of do_rootfs
>     when a wic image is build. This will rebuild the image
>     if a variable needed by wic changes.
>
>     [YOCTO #8693]
>
>     Signed-off-by: Mariano Lopez <mariano.lopez@linux.intel.com>
>     Signed-off-by: Ross Burton <ross.burton@intel.com>
>     (cherry picked from commit 12c54d50ed4c321dc272beb3c6cb770965c979f1)
>
> Author: Christopher Larson <chris_larson@mentor.com>
> Date:   Tue Nov 10 14:18:20 2015 -0700
>
>     image_types: improve wks path specification
>
>     Hardcoding a full input path with zero flexibility goes against
> everything the
>     Yocto Project is about. Rework it to let the user specify the wks base
>     filename with WKS_FILE and it'll search the layers for the wks file and use
>     it.
>
>     Signed-off-by: Christopher Larson <chris_larson@mentor.com>
>     Signed-off-by: Ross Burton <ross.burton@intel.com>
>     (cherry picked from commit 8cc7f5229f5447c2183ac319dd52c7ed737ec89b)
>
> Those improve the 'wic' image support on Jethro and are merged into
> master for a while. Could those be backported?
>

Re: [jethro] Backport proposal

[Martin Jansa]

better to include oe-core ML not oe-devel.

On Fri, Feb 26, 2016 at 9:55 PM, akuster808 <akuster808@gmail.com> wrote:

> On 2/24/16 11:50 AM, Otavio Salvador wrote:
> > Hello folks
> >
> > [Cced Robert Yang]
> >
> > I would like to propuse the backport of following changes:
>
>
> Seems responsible to me.
>
> - armin
> >
> > Author: Mariano Lopez <mariano.lopez@linux.intel.com>
> > Date:   Wed Dec 30 06:52:54 2015 +0000
> >
> >     image_types.bbclass: Rebuild when WICVARS change
> >
> >     The procces to do a wic image is to save a file with
> >     variables required by wic and then call wic using this
> >     file. Because this is external to bitbake if the vars
> >     change, the image won't be rebuild; an example of such
> >     is IMAGE_BOOT_FILES.
> >
> >     This patch adds these variables to vardeps of do_rootfs
> >     when a wic image is build. This will rebuild the image
> >     if a variable needed by wic changes.
> >
> >     [YOCTO #8693]
> >
> >     Signed-off-by: Mariano Lopez <mariano.lopez@linux.intel.com>
> >     Signed-off-by: Ross Burton <ross.burton@intel.com>
> >     (cherry picked from commit 12c54d50ed4c321dc272beb3c6cb770965c979f1)
> >
> > Author: Christopher Larson <chris_larson@mentor.com>
> > Date:   Tue Nov 10 14:18:20 2015 -0700
> >
> >     image_types: improve wks path specification
> >
> >     Hardcoding a full input path with zero flexibility goes against
> > everything the
> >     Yocto Project is about. Rework it to let the user specify the wks
> base
> >     filename with WKS_FILE and it'll search the layers for the wks file
> and use
> >     it.
> >
> >     Signed-off-by: Christopher Larson <chris_larson@mentor.com>
> >     Signed-off-by: Ross Burton <ross.burton@intel.com>
> >     (cherry picked from commit 8cc7f5229f5447c2183ac319dd52c7ed737ec89b)
> >
> > Those improve the 'wic' image support on Jethro and are merged into
> > master for a while. Could those be backported?
> >
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>

Re: [jethro] Backport proposal

[Otavio Salvador]

On Fri, Feb 26, 2016 at 6:07 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
> better to include oe-core ML not oe-devel.

Resent.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750