Chris 'Xenon' Hanson wrote:
> My hack solution was to symlink both libiconv and libintl into
> /usr/lib, which does seem to be in the lib search path at that point,
> but that seems like a poor solution.

While poking around, I see that there is a package for a static version of bash:

ftp://ftp.openbsd.org//pub/OpenBSD/3...6p1-static.tgz

I'm guessing this would solve the problem. But, it raises a couple of other questions:


1. If the user already has non-static bash installed, will installing this package
cause problems, or will it require that the non-static package be removed first?

2. For an automated installer, how would the installer know where to get the proper
package? The URL above works for 3.8, but will be wrong for 3.9. Is there an environment
variable or string that the installer can expand to get the "3.8" or "3.9" portion of the
URL? And then, how does it figure out the exact package filename for the static version of
bash for a OS release it's never seen before? Without a heavy-duty web search,how would it
know that the 3.8 static release of bash was named bash-3.0.16p1-static.tgz? It'd be nice
if the script doesn't immediately break and need updating when 3.9 comes out.


--
Chris 'Xenon' Hanson | Xenon @ 3D Nature | http://www.3DNature.com/
"I set the wheels in motion, turn up all the machines, activate the programs,
and run behind the scenes. I set the clouds in motion, turn up light and sound,
activate the window, and watch the world go 'round." -Prime Mover, Rush.