The current implementation of weston-ini-conf does its best to generate a weston.ini "on the fly" during build based on using varflags. This however circumvents large portions of the bitbake framework for sanity checking. As such, we need to manually track these variables in a number of places so that our signature is correct and we detect changes. Further we need to (and do not currently) force the resulting packages to be marked as machine specific (as they are) rather than architecture generic (which they are not!). These issues are most easily resolved by moving to using fragments to make our config file.