Re: [yocto] OpenEmbedded sole base meta layer and poky base meta layers in sync, or not (should be The Same meta base layer, used in different distros)???

2017-10-23 Thread Burton, Ross 
On 23 October 2017 at 12:39, Zoran Stojsavljevic <
zoran.stojsavlje...@gmail.com> wrote:

> > poky is generated using combo-layer, which effectively cherry-picks
> commits from the parent repositories (in this case bitbake,
> > oe-core, meta-poky, meta-yocto-bsp).  This explains why the SHAs don't
> match, as the history doesn't match.
>
> This is exactly my original point. We should have here original repos'
> SHAs. Not "modified" ones. The "modified" note should be included at the
> end of this report (to understand the differences explained by you). For
> the better understanding from where/which repos' commits/clones are coming,
> and why.
>

The script is reporting the actual SHAs that are being built, which in my
opinion is better than reporting SHAs which are similar but are not in fact
the same.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] OpenEmbedded sole base meta layer and poky base meta layers in sync, or not (should be The Same meta base layer, used in different distros)???

2017-10-23 Thread Zoran Stojsavljevic 
> poky is generated using combo-layer, which effectively cherry-picks
commits from the parent repositories (in this case bitbake,
> oe-core, meta-poky, meta-yocto-bsp).  This explains why the SHAs don't
match, as the history doesn't match.

This is exactly my original point. We should have here original repos'
SHAs. Not "modified" ones. The "modified" note should be included at the
end of this report (to understand the differences explained by you). For
the better understanding from where/which repos' commits/clones are coming,
and why.

Thank you,
Zoran

On Mon, Oct 23, 2017 at 11:25 AM, Burton, Ross 
wrote:

> On 23 October 2017 at 10:08, Zoran Stojsavljevic <
> zoran.stojsavlje...@gmail.com> wrote:
>
>> > Or better yet use
>> > http://www.yoctoproject.org/docs/2.3.2/mega-manual/mega-ma
>> nual.html#ref-classes-image-buildinfo
>>
>> Since I am also (relatively) new to YOCTO, reading these emails makes me
>> think about dependencies between YOCTO distros and layers within distros.
>>
>> Looking what is written here, I decided to do couple of the tests on my
>> own to try to understand better how OpenEmbedded (oe-core) base layer and
>> Poky distro (with two layers on the top of oe-core) are correlated with
>> each other. As my best understanding, poky master tree should do nothing
>> more that follow dependencies (with two additional layers) on the
>> OpenEmbedded master tree.
>>
>> OpenEmbedded layer is YOCTO QEMU project on its own. And one can build
>> well known QEMU targets on single oe-core.
>>
>> In order to verify this, i did git clone (at the same time) on two
>> distros: oe-core master tree, and on poky master tree.
>>
>> Now, after building oe-core, I have the following in qemux86-64 target
>> /etc/build:
>>
>> ---
>> Build Configuration:  |
>> ---
>> DISTRO = nodistro
>> DISTRO_VERSION = nodistro.0
>> ---
>> Layer Revisions:  |
>> ---
>>
>> *meta  = master:3b413a80578caacd9a7f405f3c51a3921d78a60d*
>>
>> At the same time, for poky, I got the following (qemux86-64 target
>> /etc/build):
>>
>> ---
>> Build Configuration:  |
>> ---
>> DISTRO = poky
>> DISTRO_VERSION = 2.4
>> ---
>> Layer Revisions:  |
>> ---
>> *meta  = rocko:65d23bd7986615fdfb0f1717b615534a2a14ab80
>> -- modified*
>> meta-poky = rocko:65d23bd7986615fdfb0f1717b615534a2a14ab80 --
>> modified
>> meta-yocto-bsp = rocko:65d23bd7986615fdfb0f1717b615534a2a14ab80 --
>> modified
>> ___
>>
>> Now, the question: should meta - rocko and meta - master have (in *BOLD*)
>> the SAME master HEAD #???
>>
>
> No, they're different repositories so have different SHAs.  However:
>
> $ git show 65d23bd7986615fdfb0f1717b615534a2a14ab80
> commit 65d23bd7986615fdfb0f1717b615534a2a14ab80
> Author: Randy MacLeod 
> Date:   Mon Oct 16 11:00:44 2017 -0400
>
> README.qemu: qemuppc64 is not supported
>
> (From OE-Core rev: 3b413a80578caacd9a7f405f3c51a3921d78a60d)
>
> They're the same commit.
>
> poky is generated using combo-layer, which effectively cherry-picks
> commits from the parent repositories (in this case bitbake, oe-core,
> meta-poky, meta-yocto-bsp).  This explains why the SHAs don't match, as the
> history doesn't match.
>
> Ross
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] OpenEmbedded sole base meta layer and poky base meta layers in sync, or not (should be The Same meta base layer, used in different distros)???

2017-10-23 Thread Zoran Stojsavljevic 
> Or better yet use
> http://www.yoctoproject.org/docs/2.3.2/mega-manual/mega-ma
nual.html#ref-classes-image-buildinfo

Since I am also (relatively) new to YOCTO, reading these emails makes me
think about dependencies between YOCTO distros and layers within distros.

Looking what is written here, I decided to do couple of the tests on my own
to try to understand better how OpenEmbedded (oe-core) base layer and Poky
distro (with two layers on the top of oe-core) are correlated with each
other. As my best understanding, poky master tree should do nothing more
that follow dependencies (with two additional layers) on the OpenEmbedded
master tree.

OpenEmbedded layer is YOCTO QEMU project on its own. And one can build well
known QEMU targets on single oe-core.

In order to verify this, i did git clone (at the same time) on two distros:
oe-core master tree, and on poky master tree.

Now, after building oe-core, I have the following in qemux86-64 target
/etc/build:

---
Build Configuration:  |
---
DISTRO = nodistro
DISTRO_VERSION = nodistro.0
---
Layer Revisions:  |
---

*meta  = master:3b413a80578caacd9a7f405f3c51a3921d78a60d*

At the same time, for poky, I got the following (qemux86-64 target
/etc/build):

---
Build Configuration:  |
---
DISTRO = poky
DISTRO_VERSION = 2.4
---
Layer Revisions:  |
---
*meta  = rocko:65d23bd7986615fdfb0f1717b615534a2a14ab80 --
modified*
meta-poky = rocko:65d23bd7986615fdfb0f1717b615534a2a14ab80 --
modified
meta-yocto-bsp = rocko:65d23bd7986615fdfb0f1717b615534a2a14ab80 -- modified
___

Now, the question: should meta - rocko and meta - master have (in *BOLD*)
the SAME master HEAD #???

Something here seems not in order/not in sync?! Or...Please, you
tell/explain to me!?

Thank you,
Zoran
___

On Thu, Oct 12, 2017 at 4:19 PM, Philip Balister 
wrote:

> Or better yet use
> http://www.yoctoproject.org/docs/2.3.2/mega-manual/mega-manu
> al.html#ref-classes-image-buildinfo
>
> to get:
>
> ---
> Build Configuration:  |
> ---
> DISTRO = nodistro
> DISTRO_VERSION = nodistro.0
> ---
> Layer Revisions:  |
> ---
> meta  = master:8ca61a5464743ff85b6d26886112750d6ddd13e0
> meta-xilinx   = master:74a0d90e52cca346d05a69bbd628c6ec9e49fbcb
> meta-oe   = master:5c9a4a08844c215ebd6f2146f50de753b8e7ecef
> meta-networking   = master:5c9a4a08844c215ebd6f2146f50de753b8e7ecef
> meta-filesystems  = master:5c9a4a08844c215ebd6f2146f50de753b8e7ecef
> meta-python   = master:5c9a4a08844c215ebd6f2146f50de753b8e7ecef
> meta-multimedia   = master:5c9a4a08844c215ebd6f2146f50de753b8e7ecef
> meta-sdr  = qt5-test:dacc304b01eac7448ec1ebf0b3d0eab761c41a26 --
> modified
> meta-qt5  = master:2c3ef00f53683fbdce5b390950b49b67da85d3a1
> meta-qcom = master:bae28268a9387bb842ab7bbe8200b98c1210604c
> meta-raspberrypi  = master:9d84186870a6f9bde44575690105b9bb5e44ca24
>
> Philip
>
> On 10/12/2017 05:11 AM, Ayoub Zaki wrote:
> > Hi,
> >
> > That's easy to do :
> >
> >
> > do_install_append () {
> >
> > for layer in ${BBLAYERS}; do
> > cd $layer
> > echo -n "$(basename $layer) = "  >> ${D}${sysconfdir}/gitinfo
> > git rev-parse HEAD >> ${D}${sysconfdir}/gitinfo
> > done
> > }
> >
> >
> > add it in a recipe or add it to os-release.bbappend
> >
> >
> > On 12.10.2017 11:05, Alan Martinovic wrote:
> >> I've noticed that bitbake prints the git commit versions of the layers
> >> when the build starts.
> >>
> >> meta-python   = "HEAD:b40116cf457b88a2db14b86fda9627fb34d56ae6"
> >> meta-mender-core  = "HEAD:c3b1b465ce3a27fc7b03a6b7ef596348835cff57"
> >> meta-go   = "HEAD:514b2a80a2a4235687e92fb28328bb3e7c2d6c74"
> >>
> >> Does this information find it's way into the rootfs?
> >> If not, any suggestions on how to achieve this?
> >>
> >> The goal is to have this info available while the image is running.
> >>
> >> Be Well,
> >> Alan
> >>
> >>
> >
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto