Reinstate minimal ospack for downstreams

Some downstreams want a minimal ospack (the fixedfunction ospacks contain nginx so arguably they are not minimal enough). So let's create a minimal ospack and move the fixedfunction bits into a seperate recipe to allow downstreams the ability to create a truly minimal image.

Signed-off-by: Christopher Obbard chris.obbard@collabora.com

requested review from @em

assigned to @obbardc

added 6 commits

• a7f49914...bfeb1d80 - 5 commits from branch apertis/v2023dev2
• 132facba - Reinstate minimal ospack for downstreams

Compare with previous version

Looks good to me, the only concern is that it suffers from one of the two big problems in computer science: naming (the other two being cache invalidation and off-by-one errors).

What should we call the base recipe, other than minimal?

Maybe should we name it base and rebase hmi on op of it as well?

Now that Bosch would like to add a "IoT" image I guess this would be even more useful with the IoT recipe adding e.g. docker and other niceties.

@sjoerd?

The name is a no-go for sure; If this refactors both fixed-functin and hmi images to use a common target base recipe that make some sense but we should be careful in what we promise around these recipes as well. The images in this repositories are meant to be examples and starting points, so while it's ok if others use them as a base to purely extend we don't guarantee any future compatibility (e.g. if you use one of these as a base, you should really pin a particular version and/or take some measures to smoke-test as things may change)

In that regard, how does !503 (merged) sound?

that looks good, I will (eventually) rework this MR to use a common base recipe :-)

removed review request for @em

requested review from @em

unassigned @obbardc

mentioned in merge request !503 (merged)

closed

mentioned in merge request !546 (closed)