This is the mail archive of the cygwin@sources.redhat.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: source for setup.exe?


> On Tue, Oct 24, 2000 at 11:14:45AM -0400, John Pollock wrote:
> >is the source available for setup.exe?  I looked for it on the ftp site
but
> >couldn't find it.  I was going to look into adding a silent option to the
> >setup program and see how difficult it would be (maybe accept a parameter
> >for whether it's installation from a local directory vs. from the
internet).
> >Right now i'm getting around the problem by using scriptit to invoke
setup,
> >but that's extremely fragile (if the window titles for any of the cygwin
> >dialog boxes change, it'll break scriptit).
>
> It's available via CVS or in one of the snapshots.
>
> It's a component of the winsup directory.


Specifically it's in the winsup/cinstall directory.  Look at main.cc and
follow it to the various do_* functions to see what each dialog does.

I'm also interested in a silent install.  B20 used InstallShield which
allowed us to script cygwin's installation for our 60+ development machines
and for our 100+ customers.  1.1.4's interactive installation is slowing
that process down a little :-).

I've poked around a little bit in the setup code and it looks a little
tricky to separate the GUI input from the actual installation.  The do_*
functions popup dialogs to get input and then immediately act on the input.
Perhaps the code can be refactored so that the dialogs build a configuration
file that is passed to a (silent) install function.

I just need setup to replace the functionality found in B20's installation.
Specifically, to install the base cygwin (directory structure, dlls,
registry entries, mount table, etc) and a set of local *.tar.gz packages
(yeah, I know, "which set of packages?").  It'd be nice if the installer or
some other program could also update an installation with a given set of
*.tar.gz packages.

Obviously my needs are going to be different from other people's.  So rather
than me hacking in just my changes (and having them rejected :-), it would
be nice to hear others and see where DJ wants the program to go.  If I
remember correctly, DJ said prior versions of setup were scriptable and that
this is on the to-do list.  Maybe he already has an idea of what to do.

- Erik


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]