<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"><meta http-equiv="content-type" content="text/html; charset=utf-8"><div dir="ltr">On Dec 4, 2019, at 04:16, pascal.huerst@gmail.com wrote:</div><div dir="ltr"><blockquote type="cite"><br></blockquote></div><blockquote type="cite"><div dir="ltr"><span>From: Pascal Huerst <pascal.huerst@gmail.com></span><br><span></span><br><span>Use latest_versionstring() to find the latest tagged release for use with</span><br><span>AUTOREV. This can be useful, if you want to build the latest tagged release</span><br><span>instead of a branch. UPSTREAM_CHECK_GITTAGREGEX can be used to specify a</span><br><span>version format.</span><br></div></blockquote><div><br></div><div>Have you seen this approach?</div><div><a href="https://code.ossystems.com.br/gitweb?p=meta-ossystems-base.git;a=blob;f=classes/ossystems-srcrev-handler.bbclass">https://code.ossystems.com.br/gitweb?p=meta-ossystems-base.git;a=blob;f=classes/ossystems-srcrev-handler.bbclass</a></div><div><br></div><div>For development workflows, it would be useful to override a recipe-specific branch/tag via bitbake CLI. For production/stable release workflows, it would be useful to override a layer-specific branch/tag via bitbake CLI, which could be propagated to all recipes within the layer. This would help when maintaining multiple versions of a layer, corresponding to multiple OE versions.</div><div><br></div><div>Rich</div><div></div></div></body></html>