Re: Image dependent variables/files in included recipes

Alexander Kanavin

You have to define an additional distribution I'm afraid. It can share almost everything with the existing distro, but set PREFERRED_PROVIDER differently.


On Thu, 17 Nov 2022 at 16:22, Maik Vermeulen <maik.vermeulen@...> wrote:

Depending on the image that's being built, e.g. development vs. production, we would like to be able to include different user passwords and firewall settings.

We know this can be achieved by just having two different recipes that do the same thing, but with different variables or included files. However, we were wondering if there is a neater way?

We saw this post:
which seems to do what we want, because one recipe can install recipe-development, and the other can install recipe-production, while the recipe itself can then implement what needs to happen for either.
However, other recipes included in the images can also depend on recipe, and they shouldn't depend on one specifically. They should accept that either recipe-development or recipe-production is included. Currently we see that both the generic recipe and the specific recipe used by the image are built and overwrite each other.

What would be a neat way to achieve two variants of a recipe, and having different contents and settings in them?
Or, can we solve that other included recipes depend on one of the variants, instead of on the generic one.

Kind regards,

Maik Vermeulen

Embedded Software Engineer — Lightyear

Automotive Campus 70 —5708 JZ Helmond, the Netherlands

This email may contain information which is privileged and/or confidential. If you received this e-mail in error, please notify us immediately by e-mail and delete the email without copying or disclosing its contents to any other person. Lightyear is a trade name of Atlas Technologies B.V. and is registered at the Dutch Chamber of Commerce under number 67264298. 

Join to automatically receive all group messages.