Documentation about the relationship of dependencies and priorities #8
Description
First: Thanks for this great project. It perfectly fits my needs to build reliable images with a/b updates for raspberry pi on my boat.
I wanted to give some feedback on the documentation:
When building my first image i had some trouble, because i expected the dependencies also resulting in a built order (dependencies first..).
In the documentation i could find (afterwards):
"Recipes are always applied in the order of their priority (higher means earlier). In particular, this means that dependencies may be applied after recipes that depend on them, if they have a lower priority. Note that priorities can also be negative."
This makes it clear, but maybe you could make it more prominent as a "Tip" for example.
Maybe you could also state the design rational for this? If i understand correctly:
Dependencies: These recipes also should be enabled. No effect on build order.
Priority: Only affects build order. Higher means earlier, negative allowed.
Why do the priorities have often "priority = 80_000" trailing zeros after a "_"? Does this mean 80.000? Or 80000?
Maybe such information could be included in the "schema" part?