Rails 1.2.2

Rails
1

Yesterday I ran sudo gem update rails --include-dependencies on OS X
10.4 with
MySQL 4.1. and rails 1.1.4 working well. Now nothing works. I have
now spent a day
trying to repair the damage and have had no success. I expect I will
have to wipe
out Ruby and gem and raills and start over. People seem exuberant
about rails 1.2,
but I am getting the feeling I had about Java 4 years ago (that it was
about to sink
from its own complexity.)

Regards,
jmmiller

2

On 9-Mar-07, at 3:42 PM, jmmiller wrote:

about to sink
from its own complexity.)

Regards,
jmmiller

this kind of post doesn’t help you or us.

if you want to benefit from the community then provide context and
symptoms.

if you want to benefit the community, then provide the solutions to
your problems.

I don’t know what you’re looking for - sympathy?

Jodi

3

I agree with Jodi. If you need help then post something useful. I’ve
been running rails 1.2.2 on the mac since before it was released. So
has the rest of my team. Search Google and there are plenty of
guides.

4

I’m sorry if I annoyed you folks. I am not quite ready to ask for
help yet.
I learn more by taking the time to work on it a bit longer. I was
wondering if
you, who work more on Rails than I, feel the learning curve is getting
steeper. I do not want to start a religious argument. I seem to have
misread the title of the group.

Good day,
jmmiller

5

On Mar 9, 2007, at 4:46 PM, jmmiller wrote:

I learn more by taking the time to work on it a bit longer. I was
wondering if you, who work more on Rails than I, feel the learning
curve is getting steeper. I do not want to start a religious
argument. I seem to have misread the title of the group.

I feel that the learning curve of everything is getting steeping,
and at an ever increasing rate. :slight_smile:

Rails is great because there’s such a high rate of return on the
learning, i.e. when you do learn something new, it allows you to be
efficient enough to spend a little extra time learning other new
things…and the cycle repeats!

In any case, the problem you had was one of system administration,
not Rails itself. You took a perfectly functional development system
and made changes to it without backing it up first.

Additionally, you chose to upgrade to a new version of your development
framework without, apparently, investigating what that might mean.

I’ve done all of these things myself, and have generally kicked myself
after doing so. I do it far less frequently than I used to. That’s a
learning curve in-and-of itself, I suppose. :slight_smile:

Hang in there and keep your chin up. Rails is a very good place to be
right now. With the rate of change the core team is handing us, it will
not be boring anytime soon. :slight_smile:

–
– Tom M., CTO
– Engine Y., Ruby on Rails Hosting
– Reliability, Ease of Use, Scalability
– (866) 518-YARD (9273)

6

On Friday 09 March 2007, Tom M. wrote:

I feel that the learning curve of everything is getting steeping,
and at an ever increasing rate. :slight_smile:

That’s nothing to do with Rails, that’s called getting older. >;-)

SCNR,
Michael

–
Michael S.
mailto:[email protected]
http://www.schuerig.de/michael/

7

On 9-Mar-07, at 4:57 PM, Tom M. wrote:

Hang in there and keep your chin up. Rails is a very good place to be
right now. With the rate of change the core team is handing us, it
will
not be boring anytime soon. :slight_smile:

well said Tom. A positive response is appreciated.

jmmiller, what I said was true (imo), if unbalanced. There is a great
body of active knowledge here when you have questions.

Jodi

8

On Mar 9, 2007, at 5:07 PM, Michael S. wrote:

On Friday 09 March 2007, Tom M. wrote:

I feel that the learning curve of everything is getting steeping,
and at an ever increasing rate. :slight_smile:

That’s nothing to do with Rails, that’s called getting older. >;-)

No, the older age senility thing is why I misspelled “steeper” :slight_smile:

Technology is increasing at an exponential rate, I assure you!

–
– Tom M., CTO
– Engine Y., Ruby on Rails Hosting
– Reliability, Ease of Use, Scalability
– (866) 518-YARD (9273)

9

On Mar 9, 4:57 pm, Tom M. [email protected] wrote:

In any case, the problem you had was one of system administration,
not Rails itself. You took a perfectly functional development system
and made changes to it without backing it up first.
No, I’m not that young, I only made the changes to my sandbox.

10

I followed the instructions at Hivelogic:

and my PowerBook has Ruby 1.8.5, MySQL 5.0, Subversion 1.4 and Rails
1.2.2. My upgrade from old versions is successful. Remember that you
must install the readline library before upgrading to Ruby 1.8.5.