[ crossed posted to comp.unix.solaris and comp.unix.admin ]
Here is the situation. Our current /usr/local is mounted from the
server, and we like to "tidy up" the directory ... so that it will
become easy to maintain and upgrade installed packages in the
My questions are:
a. On host A, we currently have SERVER:/usr/local
mounted on A:/usr/local. To avoid any sort of
interruption to our users, we plan to upgrade the
various installed packages in SERVER:/usr/local
by rebuilding and installing them on (say)
SERVER:/solaris_local, and then mount SERVER:/solaris_local
on A:/usr/local when we are done with the upgrading.
Is this wise?
For packages that use autoconfig, what should we
set as $(exec_prefix)?
b. We want to have SERVER:/solaris_local to contain
the subdirectories src and bin. Within src, we
will have further subdirectories named after the
various packages we plan to install. Within each
of these sub-subdirectory, we'll have the source,
compiled binaries and etc. Would it be wise to
then link the binaries within src/package onto
For example, we have the GNU C compiler compiled
in SERVER:/solaris_local/src/gcc-220.127.116.11 and
within it, we'll have subdirectories bin, lib,
man and the file gcc-18.104.22.168.tar.gz. We then do
ln -s gcc SERVER:/solaris_local/src/gcc-22.214.171.124/bin/gcc
from within SERVER:/solaris_local/bin. Would this
scheme work? Would the lib and headers be found
by gcc when we run gcc "from" A:/usr/local/bin?
Again, what should $(prefix) and $(exec_prefix)
be set at when (say) gcc is compiled?
What the wise would say of the whole structure. Can things be
improved ... along our plan?