creation / change in weston-ini-conf.bbappend can be ignored by yocto

Closing as part of EE RC2

For Dab, changes were pushed that have all of the variables be tracked correctly. For Eel, the same was done and then on top of that .

I've had a chance to talk with Richard Purdie and Chris Larson about what we're doing here. The root problem is that while there's logic today to cover ensuring that getVar() ends up causing things to be put into the signature there's no similar logic for getVarFlags(). While this could be seen as a bug, the next issue is that since we use them in a nested fashion, we would have to make use of vardeps to manually track this usage regardless.

The immediate solution here is to vardeps lines into the places where we're adding new variables that we must track and a longer term solution would be to re-evaluate how much of this functionality is even still required. With the move to Weston 2.0 a conf file is not strictly required and we could probably move to a small series of fragments to handle orientation / output device, core required parts, and board+display specific features. We should also do our best to move away from calling out specific 'portable' touchscreens as much as possible.

This is due to I believe that we're making use of variable flags in such a non-standard way. The general problem is that we need to be making a lot more use of vardeps. I actually started down this path yesterday after seeing the comment (after seeing the fix for the eGalax screen thing). I'm going to grab this issue and run with it. I also poked some of the OE folks I know to see if this is an expected side-effect of what we're doing here

is this behaviour of missing bbappends known/reported upstream already ? Is there an entry in the yocto bugzilla that we can track ?