---Cut------- >> >> Murali, >> >> Correct, .bbappend is the way to "append" changes to the original recipe w/o >> modifying it. >> >> I don't know what you mean by "each of the repos", but yes, you would need >> to place a
In this case, u-boot, boot-monitor and linux-keystone git repos. Based on you comment, I am assuming, whatever committed to meta-ti need to point to public repo and for each of this, a .bbappend is to be added to override the SRCREV in meta-arago to pick the nightly version from the tip. Murali >> .bbappend in meta-arago-distro for every component you develop actively and >> for which >> you don't want to constantly update the recipe with the new SRCREV (or >> BRANCH or >> SRC_URI etc.) >> >> By keeping meta-ti pointing to a public git tree with a specific SRCREV >> pointing preferably >> to a release tag or a stable commit ID you are making sure that it works for >> everybody. It >> is an official TI BSP and is distribution agnostic and should be parseable >> and buildable by >> anyone out there. On the other hand, meta-arago-distro is our own TI >> distribution and you >> have more freedom there. >> >> -- >> Denys _______________________________________________ meta-ti mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-ti
