On 06/01/2020 09:04, Christian Hesse wrote:
From: Christian Hesse
The shell builtin `set` produces different output for different shells:
bash$ set | grep '^TERM='
TERM=xterm
dash$ set | grep '^TERM='
TERM='xterm'
This may break reproducible builds depending on what shell is used.
Let's
Tom Yan on Mon, 2020/01/06 08:48:
> How about printenv (without grep)?
The variables are not known in advance. This needs to match all variables
starting with "enable_" and "with_".
--
main(a){char*c=/*Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/*Best regards
Hi,
On Mon, Jan 06, 2020 at 08:48:00AM +, Tom Yan wrote:
> How about printenv (without grep)?
Portability.
"env |grep" is POSIX standardized so should work everywhere.
printenv is a BSD invention, which not all unix variants are required
to have.
(Besides, printenv on its own cannot do
How about printenv (without grep)?
From: Christian Hesse
Sent: Monday, January 6, 2020 4:04:26 PM
To: OpenVPN Development
Cc: Christian Hesse
Subject: [Openvpn-devel] [PATCH 1/1] configure.ac: replace set with env
From: Christian Hesse
The shell builtin `set`
