On 09/01/2020 05:05, Khem Raj wrote: > For such usecases, Maybe you can use floating tags ( like > 'latest-release' or 'last-good' ) and move them when needed and lock > the recipes to use them to achieve what you want.
I guess we will have to do it that way then, or we create some scripts which create an include file of the revisions we want, using the fetcher calls, as proposed by Richard. > since use of AUTOREV in public recipes is discouraged, this does not > affect public layers as much > but I do worry about alternate workflows. > >> Thanks! >> Pascal >> >> [1] >> http://lists.openembedded.org/pipermail/bitbake-devel/2019-December/020618.html >> -- >> _______________________________________________ >> Openembedded-core mailing list >> Openembedded-core@lists.openembedded.org >> http://lists.openembedded.org/mailman/listinfo/openembedded-core -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
