This is the mail archive of the
mailing list for the Cygwin project.
Re: Forcing SYSTEMROOT (opinions needed)
On Mon, May 07, 2001 at 06:11:38PM +0400, egor duda wrote:
>Monday, 07 May, 2001 Corinna Vinschen firstname.lastname@example.org 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.
I agree. The idea of a file has come up from time to time. I don't see
any reason for it. It will just slow down cygwin startup further.
If you want to store your settings somewhere, store them in the
This discussion has gotten far afield of its primary goal regarding
I guess I will make an executive decision. Lets always add SYSTEMROOT
and SYSTEMDRIVE. We'll forgo an API to control this for now (since noone
took the bait and did any research for UNIX-like ways to control this
I'll check in a patch today.
Just to put an end to this discussion. I don't like the idea of a
cygwin initialization file. Nothing that has been discussed here has
convinced me that it would be preferrable to the CYGWIN environment
variable. I'm not going to introduce YA thing for users to tweak unless
a see a clear benefit.