Steve Mills wrote in post #955228:
Unfortunately, I'm such a newbie to this, I don't have git,
Then get it.
why I need it when I use subversion for version control,
Because it's a better VCS than Subversion is. Subversion uses a less
powerful paradigm (centralized, whereas Git is decentralized) and has no
real merging algorithm, which makes branching and merging needlessly
See http://www.whygitisbetterthanx.com for more details. I don't want
to hijack this thread.
and it doesn't
get automatically installed with Ruby.
It's a pity that the only real clue is this patch and that someone
couldn't readily say what file is at fault and how to edit it.
The patch says exactly that. That's what a patchfile is: a
representation of what changes get made where.
I'll install git
You don't need to *for this patch*. See my last post: you don't need
git to apply the patch. Just use the patch command.
(But you should install git for development in general.)
and investigate further if and when I find something
that doesn't work with 1.9.1. Meanwhile I think it's poor that 1.9.2 was
released with such a major bug that rake doesn't work.
I don't think that's a 1.9.2 bug, but I could be wrong. I believe it's
a Rake issue.
Here I am trying to decide whether or not ruby on rails is as good as
everyone makes out, and whether to adopt it and invest a great deal of
time in it, and I'm put off by such hurdles at the very first step.
You can use Ruby 1.8.7 if you'd rather.
But everything in Rails development is harder on Windows, or so I'm told
(I personally stay as far away from Windows as I can).