* Michael Habibi <mikehab...@gmail.com> [160825 23:26]: > The difficulty I have is thus:
> my_git_repo/ <--- what my platform developers will 'git clone' > my_git_repo/yocto_git/... <-- yocto framework > my_git_repo/yocto_git/meta-openembedded <-- another git repo nested > inside yocto repo > my_git_repo/yocto_git/meta-intel <-- another example layer. > I would like for developers to be able to 'git clone' a single repo, > but pull down all the necessary layers from various git repos. > Basically it will comprise all repos, including yocto, OE layers, > intel layers, etc. > I believe the only way I can nest submodules inside pre-existing repos > is for me to create a local clone of yocto git and add the submodules > to that clone. That means the master git repo (my_git_repo in example > above) will point to *our* clone of yocto git and not yocto project's > git repo. In our local clone of yocto git, I will add a submodule for > each layer I want to add. > Does that make sense? Is this the right approach or is there a smarter way? I'm using submodules, but I put them like: my_git_repo/ <--- what my platform developers will 'git clone' my_git_repo/yocto_git/... <-- yocto framework my_git_repo/meta-openembedded Well, I'm using bitbake and openembedded-core repos directly instead of yocto, but that doesn't really matter. Cheers, Anders -- Anders Darander, Senior System Architect ChargeStorm AB / eStorm AB -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
