On 2018-12-17 04:14, Bob Cochran wrote:
On 12/12/18 5:35 PM, John Matt wrote:Repo, git submodules or something like kas is a matter of taste and preference. Biggest advantage of repo is that a single small XML file can define a complete build or set of builds. Submodules are standard Git functionality. So you don't need to distribute or maintain an extra tool.Hi Bob,
I changed from repo to submodules to be able to organize the top level project the way I want. For me, the custom layer(s) could be the main git project with the mirrors of the external ones added as submodules. This makes maintaining small projects with relatively static use of external ones more convenient. Maybe I will try kas as well to compare it with the other two I used.
I would always recommend to have a local mirror of all sources for availability and archival purposes. You cannot be sure that someone for example does a forced commit in a public repository, removing the commit your release was pointing to.
Currently, I am debating if I need to copy the YOCTO repo to my local git (we have an internal git), or use the YOCTO repo externally, and only manage my recipes in my internal git in my organization?
We set up a poky folder on each build machine and then clone all the Yocto related repos under it (e.g., meta-openembedded, meta-raspberrypi, etc.).I try to avoid all too much custom scripts. They cost a lot of time to create and debug, especially when used by multiple persons. However, in a complex setup good tooling might even be helpful to perform most common use cases without too much training or explanation.