[yocto] Git tool/command problems with YOCTO Open Source repos

[Stefano Babic]

Hi Zoran,

On 28/11/18 12:00, Zoran Stojsavljevic wrote:
> Hello Stefano,
> 
> I am (almost) perfectly aligned with kernel.org, and I (personally)
> decided to use git. Since I start understanding importance of Linus.
> Linux officers and their Linux philosophy.

Each tool is thought to solve a specific issue. git is a configuration
management tool, and yes, it is a great tool.

> 
> Now... Answers to your email. KAS (Siemens developed tool by Jan
> Kiszka and his crew) is the supplement for the fast/quick building the
> YOCTO, to use ONLY rootfs.

It is a support to synchronize layers and to support bitbake.

> NOT kernel. NOT aligned with the git tool.
> Not applicable for purposes as git.

Each project has its own configuration management, nowadays mostly git.
But OE can use git / mercury / subversion. Your initial question is
quite a complain why tags are not used in OE, and git describe does not
work. Nevertheless, because layers are not part as a single big repo,
you need some way to sync the layers. kas is one of these tools.

> 
> On the other note, repo is GOOGLE tool. Promoted by them. Most of the
> ARM followers (such as Toradex) use repo tool.

There are people happy working with repo. Everybody chooses the tool
more suitable for own needs.

> 
> You say: I talk to the wrong crew. I think opposite. I am giving the
> generic message via YOCTO email list, to avoid hundreds of particular
> emails, so we can unify the effort. Which is not minor. Rather
> opposite: major.
> 
> Since, I guess, this is of the major importance. For YOCTO survival.
> The direction is one: git tool. For all YOCTO developers. IMHO.
> 
> Stefano,
> 
> You, as major official representative of U-Boot philosophy (and
> Wolfgang's Denk right hand),

You're now completely off topic.

> do not take sides, rather ad-hoc
> approach. For you, this topic is not important. Appreciated your help.
> 
> I am asking here for much higher awareness. YOCTO better survival in The Future.
> 

Best regards,
Stefano

> Thank you,
> Zoran
> _______
> On Wed, Nov 28, 2018 at 10:52 AM Stefano Babic <sbabic at denx.de> wrote:
>>
>> Hi Zoran,
>>
>> On 28/11/18 10:17, Zoran Stojsavljevic wrote:
>>> Hello YOCTO people,
>>>
>>> I would like to use standard git tool while using all the Yocto
>>> layers. NOT only Poky repository (which, I believe, works all the way
>>> with git tools), but as much as possible with other github proprietary
>>> repos and layers. Since I am not able to execute git commands using
>>> some number of proprietary repos over github.
>>>
>>> As example, I'll use meta-bbb repository.
>>> https://github.com/jumpnow/meta-bbb.git, after cloning the following
>>> happens (chosen, since it has at least dozen of branches):
>>>
>>> After cloning, I did not get anything from the following commands,
>>> being in the root of the meta-bbb repo, namely:
>>>
>>> [user at fedora28-ssd meta-bbb]$ pwd
>>> /home/user/projects2/beaglebone-black/yocto-master/meta-bbb
>>> [user at fedora28-ssd meta-bbb]$ git describe
>>> fatal: No names found, cannot describe anything.
>>
>> I understand, but why is this an issue in Yocto project ? The maintainer
>> does not use tags and git describe is fast useless.
>>
>> You should contact layer's maintainer and ask for that. Anyway, outside
>> poky, tags are quite unused in layers.
>>
>>> [user at fedora28-ssd meta-bbb]$ git tag
>>> [user at fedora28-ssd meta-bbb]$ git checkout thud
>>> Branch 'thud' set up to track remote branch 'thud' from 'origin'.
>>> Switched to a new branch 'thud'
>>> [user at fedora28-ssd meta-bbb]$ git checkout sumo
>>> Switched to branch 'sumo'
>>> Your branch is up to date with 'origin/sumo'.
>>> [user at fedora28-ssd meta-bbb]$ git describe
>>> fatal: No names found, cannot describe anything.
>>> [user at fedora28-ssd meta-bbb]$
>>>
>>> The rationale behind this request: git is the powerful tool which
>>> should work and be solely used for YOCTO layers' synchronization. In
>>> other words, YOCTO should give some tools' (namely git) unification
>>> guidelines in some way. :-)
>>
>> It is clear that a tool to maintain the layers in sync is required, but
>> it is quite independent how the layers (and many are proprietary layers)
>> are built. So you can use "repo" or "kas" (my preferred one) for that.
>>
>> Best regards,
>> Stefano Babic
>>
>> --
>> =====================================================================
>> DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
>> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
>> Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
>> =====================================================================


-- 
=====================================================================
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================