This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] test-in-container: Do not set GCONV_PATH, LOCPATH
- From: Zack Weinberg <zackw at panix dot com>
- To: DJ Delorie <dj at redhat dot com>
- Cc: Florian Weimer <fweimer at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Tue, 21 May 2019 10:04:15 -0400
- Subject: Re: [PATCH] test-in-container: Do not set GCONV_PATH, LOCPATH
- References: <87lfz09ctu.fsf@oldenburg2.str.redhat.com> <xno93whrej.fsf@greed.delorie.com>
On Tue, May 21, 2019 at 9:24 AM DJ Delorie <dj@redhat.com> wrote:
>
> Florian Weimer <fweimer@redhat.com> writes:
> > Sorry, I don't understand. Why would the user want to run distcc *in
> > the container*?
>
> That was just an example of an environment variable that affects the
> build. I don't know what environment variables affect the test cases.
> Timeout-related? Without a review of *every* test that might be run in
> a container, we won't know what environment variables are valid for the
> user to specify.
Maybe we should filter the environment, but have a mechanisme for
explicitly setting environment variables within the container? For
instance, setting CONTAINER_ENVNAME=value could translate to
ENVNAME=value within the container.
zw