Re: Why PREFERRED_VERSION setting of <distro>.conf overruleslocal.conf setting ?

["Hauser, Wolfgang (external)" <Wolfgang.Hauser.external@eads.com>]

> well. if you want so many changes to an existing distro then something
is wrong
> with your distro choice. Few changes can be covered as it should be.

Don't understand me wrong, a little example what I mean:

I want to use some features in busybox the original DISTRO version don't
use (and the pinned package don't provide), other features of the
original setting I don't need or not allowed to use.
Therefore I have to use an overlay containing my needs (just a different
defconfig for the needed version of the package).

Additionally I need a very minimal busybox configuration for a
maintenance system on the same hardware. Therefore I have to use an
additional defconfig placed in a different package or overlay.

Both are very individual settings and are only flavors of the same
version of the busybox package.

One way to cover this needs is using different local.conf files
containing the different packages I want to use.
(setting preferred provider and version). --> needs the leading of
local.conf
May be can be done by the _local override as suggested, I have to try
it.

Other way is to create an individual distro or machine configuration in
my overlay, which drops me from the improvements of the main repository
and I need to cover all sub settings of the source machine or distro
settings in my own target distro or machine settings. 
This procedure is a waste of work and is error-prone in my opinion.

A good way may be the handling of different flavors of the same package
by supporting sub configurations of the package by creating
individual packages with different configurations. Resulting in e. g.
busybox-<confx>-x.x.x packages I am able to install in an image.
For myself I don't have the knowledge to do such a change in bitbake or
OE.

Regards
Wolfgang Hauser