9389 2016-04-05 03:18:44 +0000 oeqa: split configuration from the code 2016-08-16 22:46:02 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 2.2 x86 Multiple RESOLVED WONTFIX Medium enhancement 2.2 M3 9390 1 liezhi.yang jose.a.lamego benjamin.esquivel leonardo.sandoval.gonzalez meta.mr.watcher meta.watcher --- --- No (bug/feature does not impact docs) oldest_to_newest 60776 0 liezhi.yang 2016-04-05 03:18:44 +0000 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 61804 1 leonardo.sandoval.gonzalez 2016-04-28 15:58:04 +0000 Robert, where do you suggest to place the conf file? 61824 2 liezhi.yang 2016-04-29 06:10:13 +0000 (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 63354 3 jose.a.lamego 2016-06-27 17:31:49 +0000 Updating target milestone. Patches send pending. 65252 4 jose.a.lamego 2016-08-16 22:46:02 +0000 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