Hi,
I brought this up on IRC with Ross, the question was if
*_BACKFILL/*_BACKFILL_CONSIDERED are necessary nowadays. I used
DISTRO_FEATURES_remove = "ldconfig"
and even though I did not add it to DISTRO_FEATURES_BACKFILL_CONSIDERED,
I did seem to have successfully removed it from DISTRO_FEATURES. I'm
assuming it is because the _append/_remove operators are always applied
at the end of any variable expansion, thus they are applied after the
python magic in base.bbclass.
The _BACKFILL/_BACKFILL_CONSIDERED magic was added in OE-Core in 2012,
commit 738658d9d5ddef026d2929188744aa225324bf26.
The _remove datasmart operator was added to Bitbake in 2013, commit
9c91948e10df278dad4832487fa56888cd58d187.
It looks to me like the _BACKFILL code was added so that new default
values could be added, without breaking existing distro conf's that used
the '='-operator to set distro features. But isn't this a general
problem for any variable that is set in user conf-files ? Why special
handle DISTRO_FEATURES and MACHINE_FEATURES ? Could we just remove the
_BACKFILL magic ?
Jacob
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#1075):
https://lists.openembedded.org/g/openembedded-architecture/message/1075
Mute This Topic: https://lists.openembedded.org/mt/74369459/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
