setup revisit

Robert Collins
Fri Mar 23 00:29:00 GMT 2001

What's the general take on the following two options:

1) Setup.exe does everything. It's all in the one exe, there's no
"bootstrapping" concept.
2) Setup.exe downloads a _very_ minimialistic cygwin environment, and
then uses that to do the rest of the install. Such an environment might
consist of cygwin1.dll, tar,rpm,rpmfind.

*less to go wrong,
*it's all pretty all the way.
*it's _much_ harder for us to leverage unix tools (and remember that
also impacts getting contributors). *Understanding symlinks is also
*Users can't upgrade userland tools from within cygwin.

* very easy to leverage unix tools.
* much more flexability.
* contributors can work with the native interface to the packaging
format. This includes things like automatic menu driven config prompts..
Note that included menus should be data driven so we can probably make
them GUI fairly easily.
* it won't be pretty when the real work occurs -- at least not unless we
include gtk+/win32 and a gui rpm/rpmfind!
* The "bootstrap" intial tarball will be around 1-1.5 Mb (cygwin1.dll is
600 Kb on it's own).

I'm in favour of 2 - IMO we'll get more code reuse and faster turnaround
time. (All the code for resumable downloads is already written for


More information about the Cygwin-developers mailing list