------art_5929_3057089.1153349230341
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On 7/19/06, Sean O'Halpin <sean.ohalpin / gmail.com> wrote:
>
> On 7/19/06, Simon Kröçer <SimonKroeger / gmx.de> wrote:
> > Curt Hibbs wrote:
> > >
> > > Its more likely that the one-click installer would continue to be a
> binary
> > > distribution (with binary extensions), but with an compiler toolchain
> that
> > > allows users to build additional extensions from source or, even
> better,
> > > provides a known target RubyGems packagers to create gems that require
> > > compilation.
> > >
> > > Curt
> >
> > I'm just curious, why would you distribute binaries if you have to
> provide
> > the compiler toolchain anyway?
> >
> > (if we had a build farm, that would be another story)
> >
> > cheers
> >
> > Simon
> >
> Hi Simon,
>
> I was suggesting two installers - one for those who just want an easy
> no-fuss one-click binary installer with everything on (the majority)
> and one for extension developers who need a reference environment
> against which to build extensions. You don't need the MinGW + MSYS
> environment bundled - you can get that off the net - it's the patches
> and tweaks, etc. that have been used to create the one-click binary
> version that you'd want in the developer version (i.e. a way to
> reproduce exactly a copy of Curt's development environment :). But if
> you did bundle MinGW + MSYS, it would add around 77MB.
>
> Regards,
> Sean
>
>
At 77MB, it would have to be an optional add-on.

For those intrepid souls who want to build  the  one-click installer distro
from source, it is itself an open source project, so that is entirely
possible.

Curt

------art_5929_3057089.1153349230341--