From: Jim Crigler <criglerj@...>
Date: 2005-11-03T00:02:07+09:00
Subject: Rubygems, FreeBSD, Nitro not all playing together nicely

I installed Rails to tinker with on my FreeBSD 4 box.  Because of
the waythe FreeBSD port (FBSD's term for installable applications)
of Rails works, rubygesms got installed with it.  So far, so good.
I can do all the rails stuff I expect to be able to do, use
tutorials, start prototyping my application, etc.

When I heard about the Nitro and had explored the documentation
(what there is of it), I decided to give it a try.  So, because
there is no FreeBSD port for Nitro yet, I entered (as root)

    gem install --rdoc -y nitro

and a few minutes later all was set up.  However, the paths
or something are not set correctly.  As an example, I tried
to start at the very beginning (a very good place to start,
I'm told), with the command

    nitrogen app myapp

and I discovered that neither nitro nor nitrogen was not in
my path (the way all the rails paraphenalia was).  Okay, it time
to start investigating.  So I read up on rubygems in PickAxe 2,
and I discovered that a few settings may be needed.  Next
iteration:

    ruby -rubygems -e 'require_gem("nitro"); load("nitrogen")' app
myapp

I got several (more than 25) warnings about '&' and '*' being
interpreted in some way (as an operators?) then an error message
(that I don't remember at the moment --- I can post it tonight
if there's a need and no one has the magic bullet for this).

I suspect is the problem is in the way FreeBSD treats gems that
*are* ports vs. gem installation of things that *aren't* ports.
I was hoping someone here might have already blazed the trail
and I just didn't pick up the signs.
--
Jim Crigler
  "I say, Jerry!  You'd be in a Blazing bad way, if recalling to life
  was to become the fasion, Jerry!"             -- A Tale of Two Cities