Re: Introducing a BUILD_ENV?

[Joerg Sonnenberger <joerg%bec.de@localhost>]

On Tue, Oct 19, 2021 at 11:29:39AM +0200, Thomas Klausner wrote:
> On Sat, Oct 16, 2021 at 05:22:14PM +0200, Olaf Seibert wrote:
> > For updating the emulators/simh package, it would be useful to have a
> > BUILD_ENV variable. It would be like CONFIGURE_ENV and TEST_ENV:
> > added to MAKE_ENV when running do-build (${BUILD_MAKE_CMD}).
> > 
> > The use case for this is that I wanted to separate out the tests, which
> > normally run as part of the build. They can be disabled by setting
> > TESTS=0, which would nicely fit in BUILD_ENV.
> > 
> > Setting TESTS=0 in MAKE_ENV would cause it to be included in do-test as
> > well, which would not help.
> > 
> > I worked around it by defining BUILD_TARGET= TESTS=0 all, but that's
> > ugly and pkglint doesn't like it either.
> > 
> > Or is there some other way to approach this?
> 
> Before adding a global variable for just one package:
> 
> Does it work if you add TESTS=0 to MAKE_ENV and TESTS=1 to TEST_ENV?

MAKE_ENV is appended to TEST_ENV, so that wouldn't work. But adding it
to TEST_FLAGS should work.

Joerg