On 2019-9-1 10:39 , Blair Zajac wrote: > > I’m not convinced that build.env is honored all the time.
There is certainly a bug where the code that parses *.env will silently stop as soon as it hits something it can't parse, which means that variables that are present in the option might not end up actually set in the environment in that case. In master/2.6 the code has been rewritten and will print a warning about the invalid entry before continuing to process the remaining valid ones. - Josh