>>Thank you Bruce. After enable kernel-devsrc, the necessary rpm had been created. >> >>I have one question though, the kernel-devsrc does not seem to include all the kernel src, that has been fetched and applied patches. Why does it call kernel-devsrc instead of just kernel-dev? Is there a way to generate rpm for a complete kernel src with patches applied? >> >Correct. It only has enough of the build artifacts to develop against the running kernel, i.e. out of tree modules (either on the build host, or on target).
>The name is historical, and isn't aligned with any specific distro (i.e. no matter what folks say, there is no agreed upon naming for these packages, so rather than break expectations in the ecosystem, we keep ours as it was: >kernel-devsrc). >To keep it minimal, we do use a curated version of the source (just like redhat, etc). Footprint is very important for that package. >That being said, I do have a patch that creates a 'linux-source' package that is the complete source, but that is really only for reference and isn't extensively tested for building/development. I'm not in a place that I can get that >patch right now, but I can send it out a bit later today. >Out of curiosity. What is the use case that you have for the source ? With that information, I can tweak what we are offering as needed. >Bruce I was asked to find a replacement of a discontinue support that provides RPMS (like, dhcp, openssl, openslp, kernel, kernel-dev, kernel-src, and etc...100+ more rpms) to the embedded system build flow. The next level team uses these rpms to build the embedded system image. I also was asked to minimize the change to the down stream team that uses these rpms. It is not clear to me why this team is using both kernel-dev as well as kernel-src... Proving that a method to generate kernel-src is not available yet, I'm going to omit the kernel-src, for now. I will see if the down stream team can continue the work without it. If I have to, I will post another request for the patch to generate kernel-src. Let me know if this does not answer your question. Thank you again. Best Regards, Michael Y. Lim HW VPD Template Boston SFO Office: 045/C-08 Tie Line: 363-7244 Phone: (512) 286-7244 email: [email protected]
-- _______________________________________________ linux-yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/linux-yocto
