RE: Bug in startxwin.bat after installing with setup.exe in win98SE

["Robert Collins" <robert dot collins at syncretize dot net>]

> -----Original Message-----
> From: Nicholas Wourms [mailto:nwourms@yahoo.com] 
> Sent: Sunday, 14 July 2002 10:24 AM

> > I mind. Setup should become -more- data driven not less. 
> > 
> 
> Excuse me?  All I was suggesting is to reword the final setup 
> screen to
> something like the following:
> 
> -Create Icon on Desktop for Cygwin Command Prompt
> -Create Icon on Desktop for Cygwin/XFree86
> -Add Icon to Start Menu for Cygwin Command Prompt
> -Add Icon to Start Menu for Cygwin/XFree86
> 
> Then have setup create the shortcuts in the same fasion it 
> does already. 
> Eventually, I'd like to have it gray-out the check boxes for
> Cygwin/XFree86 if it is not already installed.  How is this not data
> driven?  Isn't this what the setup program is for?  The last time I
> checked, most Windows installers handled the shortcut creation.

If you need to recompile setup.exe to change it's behaviour, it is not
data driven. Most windows installers are driven by an data that drives
the dialogs. 

The 'right' way to do it, is something like the menu's that dpkg uses,
they are pure data, and can be interpreted and shown as gui interfaces,
or as text menus, or set via the command line.

So, here are some options:
1) Implement an interpreter for dpkg's configure menus in setup.
2) Create something new along similar lines.
3) Use a slang interface or something like that in the postinstall
script (*).

Rob

(*) Is problematic - what happens when we start redirecting the
postinstall output to log it.