From: ts Date: 2002-07-28T21:04:45+09:00 Subject: Re: Questions about installing in a corporate WAN >>>>> "J" == Jim Freeze writes: J> 1) A statically linked ruby. J> This may or may not be the best solution. I have considered J> this becuase there is one site that may not have the standard J> libraries (see ext/Setup) needed to have ruby execute J> successfully. I have tried static linking, but the .so J> files are still required. I am definitly lacking in my J> understanding of static/shared libraries. Well, if you want a statically linked ruby, you must compile it with -static but I think that it's not possible to do it on Solaris J> a) have each sysadmin install ruby as they see fit. J> This means setting the with-sitedir as they wish. The installation of ruby is made from the official ruby distribution (ie. ruby-1.6.7.tar.gz) or this package can be modified ? J> b) have the wrapper set RUBYLIB (and possibly DLN_LIBRARY_PATH) J> so local installs can find the ruby libs pushed out in the workflow. If you can modify it, just add an extension which will be build *statically* when the sysadmin install ruby and this extension just modify RUBYLIB (internally). Because it do this when ruby call the initialisation you don't have problems with $SAFE Guy Decoux