Re: [OE-core] [PATCH] buildhistory.bbclass: metadata-revs show repo parent

[Trevor Woerner]

On 03/12/16 16:54, Burton, Ross wrote:

On 12 March 2016 at 04:28, Trevor Woerner <twoer...@gmail.com 
<mailto:twoer...@gmail.com>> wrote:

    openembedded-core/meta =
    master:00d3fd571a8d261d065b43f5cf3076a381843984
        meta-openembedded/meta-oe =
    master:a1e135a499998add7575682bf53db5e02e753580
        meta-openembedded/meta-gnome =
    master:a1e135a499998add7575682bf53db5e02e753580
        meta-rpb          =
    master:203903ca6f4e8df09bef6ea3c6e899d07eca8df9
        meta-96boards     =
    master:2be59f0d381b5ec173d7fc24f3ae14aaf47b8649
        meta-qcom         =
    master:32fcda819acb8ec485d9ab05108d554f807bf75d
        meta-browser      =
    master:a3789a4168fcd42f1cdf5b5febe2c779a9467919
        meta-linaro/meta-linaro-toolchain =
    master:367f784b831938dc508b7d472342d2d0d6ed9769
        meta-poky/meta    =
    master:37b61b059031e3c272a929b834e12fd83f46598c
        meta-poky/meta-poky =
    master:37b61b059031e3c272a929b834e12fd83f46598c


Why are you pulling oe-core/meta and poky/meta into the same build 
considering they're literally the same layer?  You should either drop 
oe-core/meta or poky/meta from your bblayers.

Ok, thanks; good point.


However the output showing the full remote URLs seems a sensible 
improvement to me.


My hesitation is whether we want to replace the existing 
buildhistory/metadata-revs with my "improvements" or whether I should 
just create a second file with the updates. I don't want to break 
anyone's process should they have come to rely on that file being as it is.
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core