I haven't been that involved with Baserock recently; sorry it took me a
while to get to this!
On 28/09/15 10:44, Adam Coldrick wrote:
> The openstack dir (for example) would contain systems and strata
> specific to openstack. Those systems and strata would refer to strata
> and components from the baserock set (or override them with their own
> things) as needed.
Where would things which aren't "core" but used in various places be
kept? I have in mind things like the databases, django and apache
strata, but there are probably many other such things too.
This is a really important point. When I was working on making
definitions for OpenStack components (and later, OpenBMC components),
this was often the case. Python components are often shared, along with
anything todo with networking (in my experience, anyway!). A shared
folder will quickly balloon; I think we'll see the same problems that we
currently have with strata, just one level higher.
Also, do you have an idea on how the overrides should work? It seems
me that we'd either need to modify the build tool to support an
`override:` field or also override everything that depends on the thing
Just a note that I've found it much easier to work out 'what
instructions + what source builds what thing' in Baserock than in an
alternative build tool, due to the lack of overrides. I haven't phrased
that well but I think it matters.