oniro-linux.conf: Rethink how DISTRO_FEATURES/IMAGE_FEATURES are defined

Right now, we do a remove in DISTRO_FEATURES. While we don't necessarily support those features, due to the finality of :remove, we force our endusers to not use them either.

By moving DISTRO_FEATURES:remove to DEFAULT_DISTRO_FEATURES:remove, we enable endusers to turn those DISTRO_FEATURES back on if needed.

We also move IMAGE_FEATURES from a distro level variable to the image. IMAGE_FEATURES should generally be put in image recipes per YP docs. This also gives end users a way to use Oniro and work around our :remove defaults.

Signed-off-by: Eilís Ní Fhlannagáin pidge@pidge.org

requested review from @agherzan and @idlethread

assigned to @pidge

approved this merge request

added 47 commits

• dee3ae86...d727b649 - 46 commits from branch eclipse/oniro-core:kirkstone
• 0346ec64 - oniro-linux.conf: Rethink how DISTRO_FEATURES/IMAGE_FEATURES are defined

Compare with previous version

approved this merge request

approved this merge request

added 2 commits

• d0a360ac - 1 commit from branch eclipse/oniro-core:kirkstone
• e55421a7 - oniro-linux.conf: Rethink how DISTRO_FEATURES/IMAGE_FEATURES are defined

Compare with previous version

enabled an automatic merge when the pipeline for e55421a7 succeeds

merged

While you might thought you sneak this in while I am on vacation I still do some post-merge reviews. :-D

But don't worry, I am fine with this approach.