[bitbake-devel] [PATCH v1] bitbake: fetch2/git: add SRC_URI option versiontag

[Rich Persaud]

> On Jan 6, 2020, at 10:15, Pascal Huerst <pascal.huerst at gmail.com> wrote:
> 
> Hey Rich,
> 
>> On 29/12/2019 03:04, Rich Persaud wrote:
>>> On Dec 4, 2019, at 04:16, pascal.huerst at gmail.com wrote:
>>> From: Pascal Huerst <pascal.huerst at gmail.com>
>>> Use latest_versionstring() to find the latest tagged release for use with
>>> AUTOREV. This can be useful, if you want to build the latest tagged
>>> release
>>> instead of a branch. UPSTREAM_CHECK_GITTAGREGEX can be used to specify a
>>> version format.
>> Have you seen this approach?
>> https://code.ossystems.com.br/gitweb?p=meta-ossystems-base.git;a=blob;f=classes/ossystems-srcrev-handler.bbclass
> 
> Thanks for the hint, this goes into the right direction, but does not
> solve my problem.
> 
>> 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.
> 
> That's exactly how we manage our development releases, but what I wanted
> to achieve with this patch is to just tag releases in our repositories
> and let bitbake figure out the latest releases to create an image from
> it. That way we don't have to fiddle around with bitbake CLI or yocto at
> all, but can just tag releases in our repositories.
> 
> I find that quite useful, but the interest has been near zero for that
> patch and I'm not sure, whether this is such an exotic use-case or if
> there are quality issues with my patch...?

Maybe start a thread on another mailing list (oe-arch? oe-core?) to collect requirements for related workflows, so your patch can be generalized to address more use cases, before extending the syntax for bitbake invocation?  There may be other bitbake improvements that OE developers have done downstream, which could be consolidated.

Rich