I’ve noticed that the -I switch for passing in search paths has also
gone
away. In the binary release John talks about a batteries included
approach.
Does that mean all we have to do is extract it to a folder, add the bin
folder to the PATH variable and off we go or are there still some
switches
to pass in when we want to use rubygems etc?
The –I switch is still there. We’re still delegating to ir.cmd to run
IronRuby today. We’ll fix some of these problems now that we have a
fixed relative path layout to our libs directory. We’ll be updating this
drop to reflect this soon (and to do a few other things that we missed
this time around like enabling RubyGems support out of the box).
I’ve noticed that the -I switch for passing in search paths has also
gone away. In the binary release John talks about a batteries included
approach. Does that mean all we have to do is extract it to a folder,
add the bin folder to the PATH variable and off we go or are there still
some switches to pass in when we want to use rubygems etc?
On Fri, Jul 25, 2008 at 9:16 AM, John L. (IRONRUBY) [email protected] wrote:
The –I switch is still there. We’re still delegating to ir.cmd to run
IronRuby today. We’ll fix some of these problems now that we have a fixed
relative path layout to our libs directory. We’ll be updating this drop to
reflect this soon (and to do a few other things that we missed this time
around like enabling RubyGems support out of the box).
Will we see regular binary releases? I’m behind a particularly
draconian proxy and SVN won’t work. HTTP headers that SVN uses are
blocked. Being able to get regular binaries or even zipped source
would be so nice!
I have a mirror of the IronRuby svn at GitHub: http://github.com/petebacondarwin/ironruby.
I will manually track the svn repository on the “master” branch of this
git
repository for the time being. (The git-svn doesn’t work too well on
windows
at the moment).
I have been using it to track my implementation of the BigDecimal
library,
which you are welcome to take a look at in the “bigdecimal” branch.
Checkout the cool network graph to see what I mean: http://github.com/petebacondarwin/ironruby/network.
You can pull zipped up sources from github. E.g. The master branch
(which
is currently a copy of SVN r127) can be pulled from: http://github.com/petebacondarwin/ironruby/tarball/master.
Hope that helps,
Pete
I have a mirror of the IronRuby svn at GitHub: http://github.com/petebacondarwin/ironruby.
I will manually track the svn repository on the “master” branch of this
git
repository for the time being. (The git-svn doesn’t work too well on
windows
at the moment).
I have been using it to track my implementation of the BigDecimal
library,
which you are welcome to take a look at in the “bigdecimal” branch.
Checkout the cool network graph to see what I mean: http://github.com/petebacondarwin/ironruby/network.
You can pull zipped up sources from github. E.g. The master branch
(which
is currently a copy of SVN r127) can be pulled from: http://github.com/petebacondarwin/ironruby/tarball/master.
Hope that helps,
Pete
The DLR is going to stabilize at some point in the fall (I forget the
exact date, but probably around PDC) and have its own codeplex project.
At that time, the language repositories will start to share the version
of the DLR on codeplex.
In the shorter term, I’m updating the codeplex.com/sdlsdk bits shortly,
so I’d suggest just taking that and then changing around things to build
against the desktop assemblies. Peter has done this already, so if you
have questions he’s your man.
Daily builds for all these things are definitely something else that’ll
have to come shortly.