P
Peter Pk
I deliberately removed GEM_HOME and tried it again and it still
installed in /usr/bin/ruby
When I explicitly set it to /usr/local/lib it went into the right place.
It is possible that the setup.rb cached the prior GEM_HOME when it did
it's "configure" phase.
So it seems the only reliable way to make an explicit, accurate,
installation script is to explicity define GEM_HOME as part of the
procedure. Since "setup" isn't explicitly asking for the items and/or
showing the current settings and asking "Y" or "N" to continue. ie: like
a debian install script.
installed in /usr/bin/ruby
When I explicitly set it to /usr/local/lib it went into the right place.
It is possible that the setup.rb cached the prior GEM_HOME when it did
it's "configure" phase.
So it seems the only reliable way to make an explicit, accurate,
installation script is to explicity define GEM_HOME as part of the
procedure. Since "setup" isn't explicitly asking for the items and/or
showing the current settings and asking "Y" or "N" to continue. ie: like
a debian install script.