[Rubyinstaller-devel] Working with multiple Ruby versions
larsch at belunktum.dk
Sun Aug 24 06:55:26 EDT 2008
On Sat, 23 Aug 2008, Luis Lavena wrote:
>> I'd like the option to work with multiple ruby versions in the same
>> rubyinstaller directory, primarily to speed up 'rake' operations and to
>> avoid multiple downloads, extracts, etc. Also, the current 'cp' operation on
>> the ruby sources code when checking out from SVN is very slow.
> I was thinking that we need to establish a "label" for those different
> version, and also get rid of the checkout and copy procedure, whcih is
> suboptimal like you said.
That appears more clean to me. I'll update my approach.
> version can be tag, branch, tarball signatures, like 1_8 (for branch)
> or 1_8_6_114 for tag and 1.8.6-p114 for tarball.
> Didn't had time to take a look, gut I think that
> config/ruby_installer.rb purpose hit another wall issue. When I first
> designed it was not ready to handle all this different context, and
> turned to be smaller for what we are trying to do.
Yes, it does seem abit awkward. Some parameters can be derived from
others, such as paths from SVN urls etc. That is not so clean when
> I've been playing with a rewrite of the task, in the lines of the
> openssl one, but with another twist.
> a YAML file that specify a single download, a checkout or series of
> files (packages) for different versions like stable, current and
> Then, a parametrized rake task for ruby18 which always depend on gcc,
> zlib, openssl versions. Unless you specify, it always build stable.
> If you want a different version, just say: rake ruby18[candidate] and
> you can also tweak openssl[current] instead of the stable default.
Is the  syntax something from Rake?
> Thanks Lars for presenting those scenarios, will be cool if we have a
> formal "meeting" to discuss next steps (Gordon, you and me) --- and
> anyone that want to join us! :-D
Sure. What form?
More information about the Rubyinstaller-devel