build.sh vs. environment and mk.conf

[Alan Barrett <apb%cequrux.com@localhost>]

On Wed, 24 Sep 2008, Mikko Rapeli wrote:
> I like it when I can just try
> 'MKSHARE=no MKBFD=no CPUFLAGS=-mthumb-interwork' ./build.sh ...' quickly 

Would 'build.sh -V MKSHARE=no -V MKBFD=no -V CPUFLAGS=-mthumb-interwork ...'
be more difficult for you?

More generally, for everybody:

    Would it be good or bad if build.sh cleared the environment, so
    that the only way to set variables that influence the build was
    through "-V variable=value" flags passed to build.sh, or through
    mk.conf?

    Would it be good or bad if the default mk.conf file
    was ignored by build.sh, and if you had to specify "-V
    MKCONF=/path/to/mk.conf" if your really wanted to use a mk.conf
    file?

--apb (Alan Barrett)