This is the mail archive of the
mailing list for the Cygwin project.
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Robert Collins <rbcollins at cygwin dot com>
- Cc: cygwin-apps at cygwin dot com
- Date: Mon, 10 Mar 2003 09:49:28 -0500 (EST)
- Subject: Re: /etc/setup.conf
- Reply-to: cygwin-apps at cygwin dot com
On 10 Mar 2003, Robert Collins wrote:
> Ok, a few pragmatic thoughts:
> * When do we parse it?
> It's not trivial:
> - if we parse on startup, and the user changes the cygwin / path during runtime, should we revert to defaults?
> - if we wait for the / path to be chosen, we can't store any pre-/ dialog settings.
> - if we parse on startup, and don't revert to defaults, can anything go --wrong--?
> For now, I'm inclined to parse and set only after / is chosen.
FWIW, I agree. If the user wants to install to a different /, we don't
want to reuse the settings from the old installation.
Also, what pre-/ dialog settings are there, "download source" and
"antivirus control"? Frankly, I don't think they are worth storing in the
.conf file - mostly because a) one might want to take a different action
every time, and b) it could be enough for them to be controlled by
|\ _,,,---,,_ pechtcha at cs dot nyu dot edu
ZZZzz /,`.-'`' -. ;-;;,_ igor at watson dot ibm dot com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk!