[5254] in SIPB bug reports
Re: sipb locker reorg
daemon@ATHENA.MIT.EDU (Salvatore Valente)
Sun Mar 26 06:49:24 1995
Date: Sun, 26 Mar 1995 06:49:08 -0500
To: yandros@MIT.EDU
Cc: bug-sipb@MIT.EDU
In-Reply-To: "[5247] in SIPB bug reports"
From: Salvatore Valente <svalente@MIT.EDU>
Chad writes:
Another issue is whether to make /mit/sipb/{bin,lib,etc} symlinks to
the relevant one of /mit/sipb/arch/@sys/{bin,lib,etc}. I've heard
arguments for (yoav) and against (sal). Any suggestion should keep in
mind the folling constraints:
/mit/sipb/bin should be a symlink to arch/@sys/bin.
/mit/sipb/lib should be a real directory, not a symlink. It should
contain the usual "lib" stuff, that is, data used by programs at
run-time.
We keep some C libraries in the sipb locker. Currently, one way to
use these is to link with -L/mit/sipb/lib/@sys. This is a pretty good
idea, although an other good idea is to change things so that you link
with -L/mit/sipb/arch/@sys/lib. Either of these is an acceptable
place to put platform dependant libraries. Perhaps the first should
be a symlink to the second?
In time, maybe "decmipslib", "sun4lib", "rsaixlib", etc. should go
away...
/mit/sipb/etc should be a real directory, not a symlink. It should
contain configuration files for programs in the sipb locker. (If
there is such a thing.) It should not contain executables. The
Mosaic script should be fixed.
The major question I still have concerns the `lib or share' idea.
In particular, whether to have...
I still don't think it's necessary or useful to introduce "share" to
the sipb locker. I willing to be convinced otherwise, but nobody has
tried yet.
...
lib/exec <- scripts, etc.
...
share/exec <- scripts
...
Who cares? This is not an exported interface, and I'm not convinced
it needs an internal representation. Why should scripts be so
different from binaries? When you want to install a script for a
platform, type "make install" and a copy of the script will be
installed in the proper bin directory. This is a good idea, as
scripts will often need minor tweaks between different platforms.
What I'm saying is that I'm not sure that we need a central repository
for scripts. If we do, just choose some arbitrary name, and use it.
I kind of like "lib/scripts", although I'm not big on any particular
name.
There, I've solved all your problems. You're welcome.
Have a nice day.
-Sal.
