>     >I really don't think that the CygWin installation should 
> be included.
> 
> I disagree quite strongly.
> 
> Nothing will put off propspective users faster than having to
> download a number of different packages, all from different sources
> (tk, cygwin, ruby, etc).

I think we should provide both. Something small and easily installable, and
the complete (big), but still easy to install kit. And still there's room
for the third installation option where user grabs all the pieces by himself
and installs one by one. For that one we should provide easy to follow and
concise instructions.

The problem is bigger when you think what the user should do after he has
installed the kit. Then starts the installation of the ruby kits he needs,
but which are not included in the standard Ruby distribution. (Like RD
tools, which need RAcc and Option-Parser...)

And I feel those addendums shouldn't be in the small distro we create. They
might have a place in big one. Anyway there's a need to have the most
important ones bundled together with easy installation scripts (which could
be in Ruby).

(The rest of this mail is dreaming. Maybe it's useful dreaming.)

I guess most of the people would like to have RAA-tools, which they could
run after successful installation, which would query at dos prompt or at
Tk-window which are the kits the user would like to download *and*
auto-install.

For the sites which don't have a network connection he should be able to
create a static kit. So the procedure would be:

1) download a kit (small or big)
2) install it
3) run RAA-tools fetch additional modules (and install)
4) run create_my_own_kit.rb
5) distribute that kit to the machines
6) install or upgrade the current machine

Those last steps are quite important, as then we would have a simple way to
provide production versions for administrators, who would just drop the
package. 

	- Aleksi