Switching a recipe between git head and git tag (for a release)

Switching a recipe between git head and git tag (for a release)

[Martin Hollingsworth]

[-- Attachment #1: Type: text/plain, Size: 398 bytes --]

Hello community,

I am looking for a best practice / a simple solution for switching the SRCREV in a bitbake recipe between git master HEAD (default, used in nightly builds) and a tagged release version (needed for a reproducible release config).



How can I minimize the amount of changes necessary to the recipe when switching to a release version?



Thanks and regards,

Martin


[-- Attachment #2: Type: text/html, Size: 2288 bytes --]

Re: [yocto] Switching a recipe between git head and git tag (for a release)

[Quentin Schulz]

Hi Martin,

On Mon, Apr 26, 2021 at 12:41:18PM +0000, Martin Hollingsworth wrote:
> Hello community,
> 
> I am looking for a best practice / a simple solution for switching the SRCREV in a bitbake recipe between git master HEAD (default, used in nightly builds) and a tagged release version (needed for a reproducible release config).
> 

Look how swupdate recipes are done in meta-swupdate:
https://github.com/sbabic/meta-swupdate/tree/master/recipes-support/swupdate

Basically all variants include the .inc file where everything in common is
specified.

Then the git recipe would point to your git master HEAD (I guess you\re
using AUTOREV mechanism?) and the point releases are e.g. foo_1.5.0.bb
where you put a given SRCREV only (or even a tarball if you want).

In the git recipe, add:

DEFAULT_PREFERENCE = "-1"

This means it'll never be preferred to other recipes (if there are
others).

For your nightly builds, you put PREFERRED_VERSION_foo = "git" in
local.conf and you should be good to go (don't add it for release builds
obviously :) ).

Hope that helps,
Cheers,
Quentin