[5106] in SIPB bug reports
should SIPB TeX be in the sipb locker?
daemon@ATHENA.MIT.EDU (Albert Dvornik)
Mon Jan 16 00:55:39 1995
From: "Albert Dvornik" <bert@MIT.EDU>
To: bug-sipb@MIT.EDU
Date: Mon, 16 Jan 1995 00:55:19 EST
The current TeX install tree in project.tex-install has 41M.
That does not include
1) the Linux build
(estimate: 3-4M)
2) .pk files (bitmapped fonts) for free fonts that come with the
current TeX release and aren't in the Athena release
(estimate: I don't know, but probably around 10-15M)
3) any cruft we want to keep from the existing stuff in the SIPB locker
(estimate: I have no idea, but I'm guessing 0-5M)
This would increase the size of the SIPB locker by at least 25M.
(yeah, right.)
\begin{flamebait}
So, maybe we should just move the SIPB TeX installation out of the
SIPB locker?
As the only person who has done work on the SIPB TeX installation in
my recent (== after Calvin stopped doing it) memory, I'm hereby
declaring myself the Powers That Be, and reserve the right to make a
unilateral decision on this matter and execute it. =)
However, I'd like to hear what other people think about the idea.
\end{flamebait}
The idea would involve moving the TeX installation into a separate
locker and installing wrapper scripts in SIPB to do the right thing if
someone does "add sipb; [la]tex foo". The lib tree would also include
symlinks to make "old" values of TEXINPUTS/TEXFONTS still do more or
less the right thing. Users who don't use recursive searches for
macros and/or fonts may still need to change their environment
variables, but the change should be fairly trivial.
I don't think this discussion should happen during the SIPB meeting.
So, if anyone has any opinions about this, I'd like to have a flamage
session today (Monday) *after* the meeting. If someone can't make it,
send me mail or something...
--bert
