[OE-core] [PATCH 1/1] base.bbclass: show layer's branches/revisions in the banner info

Koen Kooi koen at dominion.thruhere.net
Wed Jun 29 16:19:33 UTC 2011


Op 29 jun 2011, om 18:14 heeft Cui, Dexuan het volgende geschreven:

> Khem Raj wrote:
>> On 06/28/2011 04:07 AM, Paul Eggleton wrote:
>>> On Tuesday 28 June 2011 07:45:09 Koen Kooi wrote:
>>>> So it works as expected, but the output is a bit confusing. I have
>>>> a few (conflicting) suggestions: 
>>>> 
>>>> 1) replace _BRANCH and _REVISION with ' branch' and ' revision',
>>>> e.g.: 
>>>> 
>>>> 	meta-archos branch          = "master"
>>>> 	meta-archos revision        =
>>>> "413933fb5f62574e38a9a1e38905ba6e9c1be4ad" 
>>>> 
>>>> 2) for the extra layers put branch and revision on a single line:
>>>> 
>>>> 	meta-archos          =
>>>> "master/413933fb5f62574e38a9a1e38905ba6e9c1be4ad" 
>>> 
>>> I'd go with option 2 over 1, personally - the list gets rather long
>>> on something like Angstrom, better to keep it short.
>> 
>> I would say to do it uniformly and treat oe-core as one of layers too
>> when emitting this info
> Ok. I'll make a new version for this.
> BTW: meta and mete-yocto belong to the same git repo actually, so do you think showing them in one line like this
> 
> meta,meta-yocto   = "master:2c2d9d7c0e942b6748bc8bd7d5980113bae9a836"
> 
> is better than showing 2 lines like this:
> 
> meta             = "master:2c2d9d7c0e942b6748bc8bd7d5980113bae9a836"
> meta-yocto    = "master:2c2d9d7c0e942b6748bc8bd7d5980113bae9a836"

That breaks with repos like meta-intel and meta-oe. Maybe something like this:

BB_VERSION                  = "1.13.2"
TARGET_ARCH                 = "arm"
TARGET_OS                   = "linux-gnueabi"
MACHINE                     = "archosa32"
DISTRO                      = "angstrom"
DISTRO_VERSION              = "v2011.06-core"
TARGET_FPU                  = "hard"
METADATA_BRANCH             = "master"
METADATA_REVISION           = "16f84804cfbe472833ff00bfd2694947eabf8e20"
meta-angstrom               = "master:fd68a073e9669fdee0a9dc0483b3d39d3e3e0b46"
meta-oe                     = "master:8a12ecca32766ecdceb72cae76e93f8aadcf3669"
meta-efl                    	same
meta-gpe                    	same
meta-gnome                 same
meta-texasinstruments       = "master:2e16e2fbd93bc00bc0a0afaf86975da7778eaa43"
meta-efikamx                = "master:70cff8742d629fd32463e3ef1bddb83f04d08dc5"
meta-nslu2                  = "master:aaf918b85d7a8155d6e7c0ff042808346998fbea"
meta-htc                    = "master:f37d05ca7450f85642cea0e43a75df10663bd8f6"
meta-nokia                  	same
meta-openmoko              same
meta-palm                   same
meta-zaurus                 same
meta-sugarbay               = "master:50661bf038a34702f3aa139c3ea0d67fbb0ce5db"
meta-crownbay               same
meta-emenlow                same
meta-fishriver             same
meta-jasperforest           same
meta-n450                   same
meta-ettus                  = "master:c34c30fa29f7ab484cc90efb9713325da8e01460"
meta-openpandora            = "master:edaf6e751f873ed7a82c1116d3d58b9a070052dc"
meta-archos                 = "master:4b689944d968b0ef4d0e9928e76c54f8a76a919a"

regards,

Koen



More information about the Openembedded-core mailing list