Re: [PATCH] test-in-container: Do not set GCONV_PATH, LOCPATH

[Florian Weimer <fweimer at redhat dot com>]

* DJ Delorie:

> Florian Weimer <fweimer@redhat.com> writes:
>> Should we perhaps start with an environment that contains just PATH, and
>> add all the *-ENV variables (but not LOCPATH and GCONV_PATH)?
>
> I hate to put in a "full clean environment" option because we don't know
> what environment variables the user might have set intentionally for
> running the testsuite (distcc, for example).  But I see the benefit of
> sanitizing the environment, both from the usual environment and from the
> command line.

Sorry, I don't understand.  Why would the user want to run distcc *in
the container*?  What reason do we have to believe that the host
environment variable settings (regarding terminal, locales and the like)
are even valid in the container?

Thanks,
Florian