8150 2015-08-11 12:44:58 +0000 Implement whitelisting for packages from imported layers 2015-10-14 07:39:53 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake 1.9 x86 Multiple VERIFIED WONTFIX High enhancement 1.9 M3 1 alexander.kanevskiy bluelightning bluelightning bogdanx.a.voiculescu jackie.huang liezhi.yang patrick.ohly poky.bs.watcher poky.watcher randy.macleod georgex.l.musat --- --- Yes (doc changes required) oldest_to_newest 52992 0 alexander.kanevskiy 2015-08-11 12:44:58 +0000 In our custom distribution we need to provide enough content in our binary package feed repositories. To populate those, we would like to use already existing layers like meta-oe from OpenEmbedded.org, but downside is that those repositories are providing so many recipes that we don't need to build or want to ship and respectively don't allow developer to build (unsupported set of recipes). Using blacklisting feature is not really possible, as package set can be often changed and list would grow fast. Thus needed functionality with behaviour "skip all recipes in layer XXX except ones explicitly allowed". Those options can be located in distro specific configuration files, and should be layer specific. E.g. allow package "gtest" from custom layer, but skip it from "meta-oe". 53088 1 bluelightning 2015-08-13 15:07:23 +0000 FWIW, a function was added to bitbake's lib/bb/utils.py in order to make this possible - see bug 7723. With that it's pretty easy to add a class that you can inherit globally that raises SkipRecipe if the recipe is from a particular layer and isn't whitelisted. 53089 2 alexander.kanevskiy 2015-08-13 15:16:25 +0000 Yes, bug 7723 was prework for this feature. It shouldn't be hard to implement as we already discussed offline with Richard and Paul. However, I've created that item specifically to get proper design on how to implement it from ideological point of view and make feature really usable. E.g. how to name variables, how to make sure that it can be properly controlled on distro configuration level, etc. 53105 3 randy.macleod 2015-08-13 21:27:06 +0000 We wrote a script to replay all commits and output a white-listed subset of a layer, preserving the original commit id in the long log. That works but it's slow, tedious and doesn't let naive users easily discover what they _could_ add without needing to clone meta-oe or find and use the layers index. We may drop the meta-oe-subset approach if a good white-list work-flow can be agreed upon. 53119 4 bluelightning 2015-08-14 11:21:31 +0000 I've put together an initial implementation here: http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=paule/whitelist 53121 5 alexander.kanevskiy 2015-08-14 14:03:38 +0000 Looks good enough for me to get to community review and initial testing. 53144 6 jackie.huang 2015-08-17 10:59:30 +0000 I tried with the patch but it doesn't work with multilib and -native cases, you may need something like: - if not d.getVar('PN', True) in whitelist.split(): + if not d.getVar('BPN', True) in whitelist.split(): or other way to properly handle multilib. 53223 7 bluelightning 2015-08-19 13:35:47 +0000 OK, I've switched to BPN, tweaked the comments a bit and sent it as an RFC patch to the OE-Core list. 53471 8 bluelightning 2015-08-27 12:38:57 +0000 Have sent a v2 with some changes: http://lists.openembedded.org/pipermail/openembedded-core/2015-August/109520.html 54060 9 bluelightning 2015-09-15 09:26:47 +0000 The patch implementing this has been rejected; the community would rather not support this kind of thing in OE-Core. Distro layers can carry and use the class if needed though. 55281 10 georgex.l.musat 2015-10-14 07:39:53 +0000 Setting as verified as per last comment.