It should be possible to inherit all settings from a parent package, but override individual properties on demand.
Currently overrides only work if you keep package name similar, and make use of the standard yaml inheritance/override system.
It's ok, but is inconvenient for testing purposes or when variations are needed.
Treat this issue critically to check if it actually is just a minor issue.
Instead of introducing yet another way of planting overrides, I should better leave it the way it is.
The following improvements were made:
'executable_alias' is now named 'alias'
delegates are looked up in order: root package, alias package, all required packages (breadth first). This fixes a common source of errors and makes it so much better already. If needed, more information can be pulled from the alias package at some point, but no I see no such need.
It should be possible to inherit all settings from a parent package, but override individual properties on demand.
Currently overrides only work if you keep package name similar, and make use of the standard yaml inheritance/override system.
It's ok, but is inconvenient for testing purposes or when variations are needed. Treat this issue critically to check if it actually is just a minor issue.