[yocto] devtool and adding specific tag from repo

Paul Eggleton paul.eggleton at linux.intel.com
Wed Apr 19 21:20:14 PDT 2017


On Thursday, 20 April 2017 10:50:19 AM NZST Brian Kurle wrote:
> I'm trying to get up to speed on devtool.
> 
> I've created a generic eSDK (poky and meta-openembedded) and installed it.
> 
> From there, I'm trying to create a new recipe, but I apparently am not
> executing it correctly to pull the desired tag.
> 
> If I execute:
> 
> devtool add --version 2.4.2 mbedtls git at github.com:ARMmbed/mbedtls.git
> 
> or
> 
> devtool add --version 2.4.2 mbedtls
> git at github.com:ARMmbed/mbedtls.git;tag=mbedtls-2.4.2
> 
> or
> 
> devtool add --version mbedtls-2.4.2 mbedtls
> git at github.com:ARMmbed/mbedtls.git
> 
> It still manages to get the wrong hash (not even the right branch).
> 
> Is this a limitation of devtool, or is a better way to do this?
> (E.g., just go to the sources directory, check it out and manually update
> the recipe?)
> 
> My goal is to set up a stock recipe off of the mbedtls-2.4.2 tag,
> where I'll then create a bbappend to add additional patches and
> configuration specific for our platform.  I could do it manually, but it
> would be nice to know how to do it "the right way" for the documentation
> I'll pass to others on my team.
> 
> Guidance and correction would be most appreciated.

For everyone's benefit, FYI Brian and I have talked offline, but there
are several bugs and opportunities for improvement here as it turns out.
I have filed the following bugs:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=11389
https://bugzilla.yoctoproject.org/show_bug.cgi?id=11390
https://bugzilla.yoctoproject.org/show_bug.cgi?id=11391
https://bugzilla.yoctoproject.org/show_bug.cgi?id=11393
https://bugzilla.yoctoproject.org/show_bug.cgi?id=11392

The current workaround for this particular example is to use this:

devtool add --version 2.4.2 mbedtls "git://github.com/ARMmbed/mbedtls;branch=mbedtls-2.4;rev=mbedtls-2.4.2"

By using the default git protocol rather than ssh, we avoid having to use
git@ which avoids triggering 11390 or 11391. Also worth noting is that
you must use quotes around the URL if you're specifying a revision
and/or branch because of the ; character, otherwise your shell will eat
that part and because something=value is a valid shell command you
won't get an error. It could be that we need to provide additional explicit
command-line options for specifying the branch/tag/revision to avoid that,
I'm not sure if there's another practical way - suggestions welcome.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



More information about the yocto mailing list