Hi there, I have a couple of questions regarding the compliance program. If there is a better place for asking such questions, please let me know.
I have studied the Yocto compliance documentation, [1] on the website, and I have the following questions: - is there any 'practical' guide with "do's and don'ts" to help make a sucessful Yocto Project Compatible registration? - i understand that while the project should build with the OE core toolchain, it is not required to use the OE core toolchain 'by default', so we should be able to provide our own modified/customized toolchain in our layers, is my understanding correct? - it is recommended, but not mandatory not use the Yocto kernel, so we can use any mainline version in our BSP layers, right? - is it tolerated to change the versions of some components from OE-core or meta-oe? Not just add patches through .bbappend, but actually use an older or a more recent version of components, let's say Gstreamer for example? - can we included new recipes for software programs not already included in oe-core or meta-oe in our layers, or do we have to contribute them back into oe-core or meta-oe before registration? - the Yocto project compatible registration is made against a specific version of Yocto. What happens when a new Yocto version is released? Should we go through the registration process again? thanks a lot! nicolas [1] https://www.yoctoproject.org/ecosystem/yocto-project-compliance-program _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
