For example, in meta/lib/oeqa/selftest/archiver.py: features = 'INHERIT += "archiver"\n' features += 'ARCHIVER_MODE[src] = "original"\n' features += 'COPYLEFT_PN_INCLUDE = "%s"\n' % include_recipe features += 'COPYLEFT_PN_EXCLUDE = "%s"\n' % exclude_recipe We can put these in a conf file, the benefit is: * The user can easily know what is happened * We can easily add or modify the test case
Robert, where do you suggest to place the conf file?
(In reply to comment #1) > Robert, where do you suggest to place the conf file? You can use a proper location you like, for example, in oeqa: meta/lib/oeqa/selftest/config_files/signing.conf
Updating target milestone. Patches send pending.
A solution was developed for the requested feature: [1], however, the change proved to be too intrusive and the resulting code hard-to-read enough to make it nonviable to implement. [1] http://lists.openembedded.org/pipermail/openembedded-core/2016-August/124867.html