Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Date: Mon, 7 May 2001 18:11:38 +0400
From: egor duda <deo AT logos-m DOT ru>
X-Mailer: The Bat! (v1.45) Personal
Reply-To: egor duda <cygwin-apps AT cygwin DOT com>
Organization: deo
X-Priority: 3 (Normal)
Message-ID: <15607524704.20010507181138@logos-m.ru>
To: Corinna Vinschen <cygwin-apps AT cygwin DOT com>
Subject: Re: Forcing SYSTEMROOT (opinions needed)
In-reply-To: <20010507153134.C24200@cygbert.vinschen.de>
References: 
 <E94FF01DFF6CD31186F4080009DC361501F8C39D AT nttwr2 DOT tower DOT bldgs DOT butlermfg DOT org>
 <20010502222849 DOT A1238 AT redhat DOT com> <20010503111926 DOT Y24200 AT cygbert DOT vinschen DOT de>
 <20010503133346 DOT A5353 AT redhat DOT com> <147585893249 DOT 20010507121105 AT logos-m DOT ru>
 <20010507114813 DOT V24200 AT cygbert DOT vinschen DOT de> <3AF69D43 DOT C5528BF0 AT yahoo DOT com>
 <20010507153134 DOT C24200 AT cygbert DOT vinschen DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi!

Monday, 07 May, 2001 Corinna Vinschen cygwin-apps AT cygwin DOT com wrote:

CV> On Mon, May 07, 2001 at 09:04:03AM -0400, Earnie Boyd wrote:
>> Corinna Vinschen wrote:
>> > Nevertheless I agree that the setting in an environment variable
>> > doesn't fit our needs in the future. Shouldn't we discuss creating
>> > a settings file which may override or supplement the CYGWIN environment
>> > variable settings?
>> > 
>> 
>> Perhaps doing away with the CYGWIN environment variable altogether.

CV> Yes, personally I strongly agree but I'm somewhat reluctant to break
CV> backwards compatibility... even if it's ugly.

i don't think it's ugly. on the contrary, configuring a program via
environment is much better and easier to administrate then using
files, etc. For example, i wrote some big script, that's supposed to
run on many machines across our company LAN. some machines in the LAN
do have installed cygwin, others don't. the script uses some cygwin
programs, so some cygwin configuration is needed. to work correctly,
this script is making some assumptions about cygwin configuration, for
example, it needs binmode, or codepage:oem, or something else. on the
other hand, i don't want to interfere with other CYGWIN settings
already set on those machines, where cygwin is already installed.
what's worse, some programs called from this script may want
nobinmode. with options passed via environment, i have no problems to
implement such script. without it it's certainly harder.

>> > We could add a CYGWIN setting ;-) like "settings_file:<DOS-PATH>"
>> > and the file could contain setting=value pairs one per line:
>> > 
>> >     binmode=yes
>> >     check_case=relaxed
>> >     error_init=C:\Cygwin\bin\gdb.exe
>> >     ntsec=yes
>> >     smbntsec=no
>> >     tty=yes
>> > 
>> 
>> Shouldn't this go into a /etc/cygwin.init file?  This would match the
>> way that UNIX sets up it's user supplied initialization values.

CV> Fine with me. But I added the "settings_file:" to be careful with
CV> using POSIX paths. POSIX paths are user defined and could point
CV> to different /etc directories. Hmm, that may not be that bad...

this may be a problem too, because we possibly don't know whom the
script will be started by. yet in the same time, i want to make it
universal, residing on network share, and working correctly no matter
who had started it and where from.

Egor.            mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19