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

[Khem Raj]

On Sat, Mar 12, 2016 at 1:33 PM, Trevor Woerner <twoerner at gmail.com> wrote:
> To me, the purpose of buildhistory's metadata-revs is to enable someone else
> (or myself in the future) to recreate a specific build, that's why I always
> save this file with any build artifacts. Simply saying "meta" isn't good
> enough because it doesn't specify which repository's "meta". So the purpose
> of this patch is to try to clarify which repositories we're talking about.
>
>> Before:
>>     meta              = master:00d3fd571a8d261d065b43f5cf3076a381843984
>>     meta-oe           = master:a1e135a499998add7575682bf53db5e02e753580
>>     meta-gnome        = master:a1e135a499998add7575682bf53db5e02e753580
>>     meta-rpb          = master:203903ca6f4e8df09bef6ea3c6e899d07eca8df9
>>     meta-96boards     = master:2be59f0d381b5ec173d7fc24f3ae14aaf47b8649
>>     meta-qcom         = master:32fcda819acb8ec485d9ab05108d554f807bf75d
>>     meta-browser      = master:a3789a4168fcd42f1cdf5b5febe2c779a9467919
>>     meta-linaro-toolchain =
>> master:367f784b831938dc508b7d472342d2d0d6ed9769
>>     meta              = master:37b61b059031e3c272a929b834e12fd83f46598c
>>     meta-poky         = master:37b61b059031e3c272a929b834e12fd83f46598c
>>
>> After:
>>     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
>
>
> I have a second patch, now, that will generate the following output, which I
> think is even better:
>
>     git://git.openembedded.org/openembedded-core.git
>     openembedded-core/meta = master:00d3fd571a8d261d065b43f5cf3076a381843984
>
>     git://git.openembedded.org/meta-openembedded
>     meta-openembedded/meta-oe =
> master:a1e135a499998add7575682bf53db5e02e753580
>
>     git://git.openembedded.org/meta-openembedded
>     meta-openembedded/meta-gnome =
> master:a1e135a499998add7575682bf53db5e02e753580
>
>     git://github.com/96boards/meta-rpb.git
>     meta-rpb          = master:203903ca6f4e8df09bef6ea3c6e899d07eca8df9
>
>     https://github.com/96boards/meta-96boards.git
>     meta-96boards     = master:2be59f0d381b5ec173d7fc24f3ae14aaf47b8649
>
>     https://github.com/ndechesne/meta-qcom.git
>     meta-qcom         = master:32fcda819acb8ec485d9ab05108d554f807bf75d
>
>     git://github.com/OSSystems/meta-browser.git
>     meta-browser      = master:a3789a4168fcd42f1cdf5b5febe2c779a9467919
>
>     git://git.linaro.org/openembedded/meta-linaro.git
>     meta-linaro/meta-linaro-toolchain =
> master:367f784b831938dc508b7d472342d2d0d6ed9769
>
>     git://git.yoctoproject.org/poky
>     meta-poky/meta    = master:37b61b059031e3c272a929b834e12fd83f46598c
>
>     git://git.yoctoproject.org/poky
>     meta-poky/meta-poky = master:37b61b059031e3c272a929b834e12fd83f46598c
>
> Frankly, there are too many forks and clones. There are too many
> meta-beaglebone or meta-odroid or meta-raspberrypi repositories. If six
> months from now I want to recreate a build I've done today, I'll need to
> know the repository, where it's from, and which commit was checked out. My
> latest patch provides that information.
>
> Is this better?

what happens if one has a local checkout forked from upstream branch ?
it reports that one, so buildhistory is expecting you to control the repos
e.g. when using tools like repo, it gets utterly confused since its meant
to track local checkout SHAs not remote ones, may be your change
can establish a better origin tracking. it would be interesting to see
how it works with repo and when I have more than 1 remotes in a single
repo