No progress installing ruby via macports. How long should this action take?

A more appropriate thing to check, when you've seen no progress, is your system's activity.

A more appropriate thing to check, when you've seen no progress, is your system's activity. On Mac OS, you could either open "Activity Monitor" and sort by CPU, or open a terminal and type top -o cpu. Watch for some app showing consistent activity, especially something with "port" in the name.To deal with the lock... odds are REALLY good it's stale since you cut it off at the knees by closing the terminal, so use sudo rm /opt/local/var/macports/registry/.registry.

Lock to remove it and retry if you want. I will recommend RVM for installing new versions of Ruby.It's really convenient. Before you jump into RVM read the "Installation" and "Rubygems" pages entirely, and after installing RVM type rvm notes and follow the directions it spits out.

Finally, do not, under any circumstance, no matter how good an idea it seems to be, try to replace or upgrade the system version of Ruby installed by Apple. Apple installed it for their own use, and messing with it invites bad juju.

Thanks. I am decided to give macports one more try. I followed your instructions to stop the lock (twice or so) until getting a message the file no longer existed, which was the objective.

I typed the original install command again and now am running into this error: ---> Computing dependencies for ruby ---> Dependencies to be installed: libiconv ncurses ncursesw openssl zlib readline Waiting for lock on /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports. Org_? Release_ports_textproc_libiconv/work/.macports.libiconv.

State – Rozey Mar 22 at 3:58 should I re-apply your rm command to this file as well? Thanks for being patient with me, by the way. – Rozey Mar 22 at 3:59 I think it's safe to delete the second lock file.It's like the old saying "In for a penny, in for a pound".

You'd already started the process by killing the terminal, then deleting the first lock file. Sometimes installs don't happen easily. – the Tin Man Mar 22 at 4:29 And I'd recommend using Cinderella to get RVM going; Cinderella brings in PostgreSQL, MongoDB, and various other things that you'll probably want to have around if you're doing Ruby work.

– mu is too short Mar 22 at 5:44.

A more recent way to install Ruby is via RVM. Not a direct answer to you question, but I would highly recommend it.

Here is another vote for rvm. If you are like me, and you program on a mac, but you deploy to some other *nix, then you can make sure you have the same version of Ruby (and Rails, and gems) on each, using rvm's gemsets. Also, you can switch among gemsets easily, so that if you find a gem that you can't get working right with Ruby 1.9.2, then you can switch to 1.8.7 or some such whilst you try to figure it out.

Stuff like that. As far as I'm concerned, you can jump right in on your mac (as yourself, not using sudo) with rvm install 1.8.7 or rvm install 1.9.2. Then make sure you switch to use the correct rvm, and make the one you want your default, and you're golden.

If it doesn't work, delete it - all the gemsets will be installed below your home directory in . Rvm/* The pain you are going through now will resurface when you try to keep your system version of Mac's ruby working with all the stuff you write -- RVM is definitely easier than using Mac's Ruby.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.