On Sun, 2018-06-24 at 03:53 +0800, Zheng Ruoqin wrote: > Add dnf-nativesdk and it's runtime dependence to make dnf work on > cross-development environment. > > Signed-off-by: Zheng Ruoqin <zhengrq.f...@cn.fujitsu.com>
I don't mind adding enough of the changes so that dnf-nativesdk is buildable so some of your other patches can be merged. I do not want to add dnf-nativesdk to meta-toolchain by default however as there are many people who don't need this there. I'd suggest this is a customisation you'll need to maintain yourselves. I appreciate why you want to do this, I also believe we have a better technique in the form of the eSDK, where we can use the same tools and the same codebase to build for example a rootfs. The eSDK use case (a locked sstate cache) is designed so that a user doesn't need to worry about a whole build, or building from scratch. They can use the same tools everyone else uses and the same workflow and code to bulld a rootfs or a recipe or any workflow. This makes it much more powerful and able to fulfil many different use cases compared to meta-toolchain. In the long run I'd therefore prefer we promote this and use the eSDK as I think it will become our preferred way of handling problems like this. Cheers, Richard -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
