On Fri, 2018-06-22 at 08:10 -0700, Christopher Larson wrote: > Yeah, I think in this case this works as a class, but you're right, > we should probably shift more to the python package. Namespacing is > probably a good idea, we've talked about doing that more in the past.
Whilst changing what we have today is hard, we can at least do better when we add new classes. I've been trying to, not sure how well its going but we can try! > In this case it's technically not image-only, though an sdk uses the > same underlying functionality, so it's debatable. I wonder if we > should namespace into a subdirectory to also make it easier to make > sense of classes/ at a command-line, i.e. inherit image/postinst- > intercepts.bbclass? Hmmm. I'd thought about image verses sdk and decided its roughly "image" and clearer this way that any other I could come up with. There is an open bug about "global" classes verses "recipe" classes too and how hard it is to tell the difference currently. I'd probably favour splitting things up a bit. I'd not considered subdirs, its worth thinking about... Cheers, Richard -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
