[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-ed] [PATCH] configure: respect user env settings

From: Antonio Diaz Diaz
Subject: Re: [Bug-ed] [PATCH] configure: respect user env settings
Date: Fri, 02 Jan 2009 13:55:21 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.7.11) Gecko/20050905

Mike Frysinger wrote:
On Thursday 01 January 2009 18:08:52 Karl Berry wrote:
No, setting variables on the cmdline is the newer/preferred way.
Setting envvars is the older/unpreferred way

i was referring to config.status and env var handling, not how to pass settings. personally i find the command line clunky when dealing with whitespaced variables as it isnt uncommon for it to fall apart in configure scripts and recursive configure scripts.

Ed produces a config.status script and correctly copies in it all the relevant variables (even the whitespaced ones) passed to configure using the method preferred by the GNU Coding Standards. BTW, I consider the use of whitespaced variables bad practice.

Environment variables are a source of unpredictability. I have never supported them in my projects and I hope they will be deprecated someday.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]