This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: Forcing SYSTEMROOT (opinions needed)
Hi!
Monday, 07 May, 2001 Corinna Vinschen cygwin-apps@cygwin.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@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19