New HS build: how to handle changes in the top-level repository?

[Erik Joelsson]

Hello Volker,

Awesome to see you working on this!

On 2015-06-16 14:42, Volker Simonis wrote:
> Hi,
>
> I'm just adapting the new HS build to AIX. The problem is that the AIX
> xlc compiler uses a different flag for the compiler command file
> option. While all the currently supported compilers use '@<filename>'
> we have to use '-f<filename>' on AIX.
>
> In order to fix this, I have to introduce a new variable
> 'COMPILER_COMMAND_FILE_FLAG' in spek.gmk and set it correspondingly in
> flags.m4. All this is in the top-level directory so my question is how
> to handle this as this requires the regeneration of
> generated-configure.sh which I can only do for the "open part". Is
> this still important in the build-infra repository (i.e. does
> build-infra still has a dependency on your 'closed source' configure
> parts?
Just push your changes to build-infra. Yes, we will then need to 
regenerate internally, but it's not a big deal. We will see the push 
notification emails and fix it as needed, so don't worry about it. 
Historically in build-infra, we had people forgetting to push the closed 
regenerated file often enough anyway.
> The other question is how to track dependencies of the new hs build to
> changes required in the top-level repo. Is this done at all or can I
> simply push the corresponding hs changes AFTER I pushed the top-level
> changes?
We don't explicitly track such dependencies, we just push what we need 
for now, to any repo in the forest. Just try to not forget to push a 
repo. :)

/Erik
> Thank you and best regards,
> Volker