Failure to load manually installed gitsh about gitsh HOT 4 CLOSED

@jmpalacios It doesn't look like you're doing anything wrong, but there is definitely a setup.rb file in the tarball, so it must have been incorrectly deleted or moved at some point in the installation process.

Could you extract the tarball again, and then confirm that there is a gitsh-0.3/vendor/gems/setup.rb file, and that the file still exists after you run ./configure, and again after you run make?

from gitsh.

@georgebrock

Same issue on my machine running Debian Wheezy.

The gitsh-0.3/vendor/gems/setup.rb exists after configure has run as well on my system.

from gitsh.

Solved this by correcting which the system ruby was supposed to be. The scripts seems to have be a bit confused as to which ruby to use.

On another note that could be of use, is that the "bin" file was aiming to use #!/usr/bin/ruby while I needed to set this to #!/usr/local/bin/ruby to ensure that the correct ruby was used instead of the fallback ruby 1.8.7.

Hope this is of use to someone.

from gitsh.

@georgebrock Thanks for the quick reply! I'm a bit embarrassed to admit I'm not really sure what happened the first time, but here's the output after trying a second time (hint: worked perfectly and gitsh is now running fine so far on OS X Lion):

-> curl -O http://thoughtbot.github.io/gitsh/gitsh-0.3.tar.gz
(snip)
 -> tar xzvf gitsh-0.3.tar.gz
(snip)
 -> cd gitsh-0.3/
 -> ls vendor/gems/setup.r
-rw-r--r--  1 jmpp  staff   147B Jan 28 10:28 vendor/gems/setup.rb
 -> export RUBY=/opt/local/bin/ruby
 -> ./configure --prefix=/usr/local/
(snip)
 -> ls vendor/gems/setup.rb 
-rw-r--r--  1 jmpp  staff   147B Jan 28 10:28 vendor/gems/setup.rb
 -> make
(snip)
 -> ls vendor/gems/setup.rb 
-rw-r--r--  1 jmpp  staff   147B Jan 28 10:28 vendor/gems/setup.rb
 -> sudo make install
(snip)
 -> ls /usr/local/share/gitsh/gems/setup.rb 
-rw-r--r--  1 root  wheel   147B Feb 12 12:52 /usr/local/share/gitsh/gems/setup.rb
 -> diff /usr/local/share/gitsh/gems/setup.rb vendor/gems/setup.rb
(no differences)

In fact, the output of make install was much longer this time round, so apparently something failed to configure for some odd reason the first time I tried, or something like that... no real idea what could have gone wrong.

In any case, this turned out into a non-issue, so I'm gonna close it. Sorry for wasting your time :( and thanks for such a nifty utility!

from gitsh.