From: Jim Freeze <jim@...>
Date: 2002-07-28T04:39:40+09:00
Subject: Questions about installing in a corporate WAN

Hi All:

I have been trying to explore various install options
for Ruby at my work. But, instead of asking about 
detailed parts of my exploration, please oblige
this posting of the install constraints. Maybe
then some well-informed individual can help me out.

We have a WAN with a workflow based un SunOS.
Every week, the workflow directory tree gets pushed
out to every office. This allows updates to the workflow
and ensures the whole company is using the same version.

It is my intention to push the sitedir out inside the
workflow tree. 

We also have a bin ditribution, where I can submit an
install package and all the sysadmins will install the tool.

It is my intention to have the ruby executable installed 
through this avenue since it is a one-time event and
only needs to occur when ruby needs to be updated.

The main issue is getting the ruby executable installed
in all locations and to use the same sitedir within the workflow
tree. I think there are several possible solutions, but I have
yet to find a solution that is comprehensive.

Here are my thoughts:

 1) A statically linked ruby.
    This may or may not be the best solution. I have considered
    this becuase there is one site that may not have the standard
    libraries (see ext/Setup) needed to have ruby execute 
    successfully. I have tried static linking, but the .so
    files are still required. I am definitly lacking in my 
    understanding of static/shared libraries.

 2) What to do about the sitedir.
    Since each admin can install ruby wherever they want,
    the install must set --with-sitedir pointing to a common
    location in the workflow tree.
    The issue I am trying to solve here is I would prefer to 
    ship an installation package that did not install to 
    any sitedir. The reasons are:
      1) sitedir may not exist
      2) if it does exist, I don't want it changed
      3) the installer may not have permissions to write to sitedir
         b) If the installer does not have sufficient permissions
            the install will fail.

  After this roadblock, I began reconsidering #1, but the internal 
  rubylib search path would have to have be customizable for each 
  installation. This I don't know how to do or if it is possible.

  My cheap solution to all these problems is this:
   a) have each sysadmin install ruby as they see fit.
      This means setting the with-sitedir as they wish.
   b) have the installation place a wrapper in the workflow path
      that will point to the local installation of ruby and irb.
   b) have the wrapper set RUBYLIB (and possibly DLN_LIBRARY_PATH)
      so local installs can find the ruby libs pushed out in the workflow.

  The part I don't like about this is the dangling rubylib search path
  compiled into each ruby executable. Plus, I don't like having to set
  RUBYLIB, since it is not valid except for $SAFE == 0.

I would appreciate any feedback or insights anyone may have
on these issues.

Thanks

-- 
Jim Freeze
If only I had something clever to say for my comment...
~