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: Florian Weimer <fweimer at redhat dot com>
- To: DJ Delorie <dj at redhat dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Mon, 20 May 2019 21:38:20 +0200
- Subject: Re: [PATCH] test-in-container: Do not set GCONV_PATH, LOCPATH
- References: <xnwoilhqq8.fsf@greed.delorie.com>
* DJ Delorie:
> Florian Weimer <fweimer@redhat.com> writes:
>> Still there is a separate Rules recipe.
>
> Sure, I'm just saying I thought about this problem when I initially
> wrote it, so we don't have to worry about if test-container itself uses
> a variable. The goal back then was "test-container should be itself run
> like any other test case". That means same env vars.
>
> So IMHO the right fix is to filter out those variables inside
> test-container.c where the child's environment is set up.
Should we perhaps start with an environment that contains just PATH, and
add all the *-ENV variables (but not LOCPATH and GCONV_PATH)?
Thanks,
Florian