[Fuego] [PATCH] Move fuego-ro/core to image during build and keep core as submodule

Tim.Bird at sony.com Tim.Bird at sony.com
Tue Feb 20 01:18:12 UTC 2018

> -----Original Message-----
> From: Guilherme Campos Camargo
> Those directories ideally shoud be copied to the image during build time
> given that Fuego would not run if their content is not available. By
> doing this, we're also making sure that a user that plans to use
> fuego-base docker image directly (or as a base image for his own docker
> images) will be able to do it straightforwardly, without the need of
> cloning other repositories or bind-mounting host's directories.
> It's also a good idea to keep fuego-core locked in a fixed release, what
> we can enforce easily by using git submodules. This is desired if we
> want to use a stable version of fuego to test new versions of fuego.
> On this patch we configure fuego-core as a submodule and make the
> changes needed for copying the required contents of the mentioned
> directories.

I understand virtually none of what you wrote here. 

Is this patch for tbird20d/fuego?  Is it against profusionmobil/fuego-release-test?

I haven't figured out how the fuego-release-test works yet, so I don't
understand what you're referring to when you say "those directories",
or "fuego-base docker image".

> --
> Tim, please let us know what you think about it.
I need to understand what's going on, and how all these repositories
interact, before I can give any coherent answer.

I think that once I've run the release test successfully, I will be able
to figure out what you're talking about here.
 -- Tim

More information about the Fuego mailing list