[1815] in SIPB_Linux_Development

home help back first fref pref prev next nref lref last post

4.2 package scheme

daemon@ATHENA.MIT.EDU (Salvatore Valente)
Sat Sep 27 17:43:02 1997

Date: Sat, 27 Sep 1997 17:42:41 -0400
To: linux-dev@MIT.EDU
From: Salvatore Valente <svalente@MIT.EDU>


A bug was fixed (by Aaron and Greg separately) in
/usr/athena/bin/latex.  I wanted to make a new tex package with the
fixed executable.  Aaron told me to run
/mit/linux/devel/package-scheme/mkspecs to update the tex package
release number.  However, this script also updates the release numbers
of all other packages, which seems like a bad idea to me.  (We
shouldn't do things that imply packages have to be updated when they
don't really.)

I've written a description of how I think package upgrading should
work.  It's in /mit/linux/devel/sals-scheme/README.  It's very, very
similar to what Aaron did, and it uses all the excellent work he's
done, but it allows for packages to be upgraded separately.  It
suggests a new script, "makepackage", which is a modified version of
"mkspecs".  I haven't actually made these modifications yet, since (a)
I don't know perl and (b) it's still in the proposal stage.  Please
look at the README file and let me know if you think it's any good,
and if you have any suggestions.

Have a nice day.
-Sal.

home help back first fref pref prev next nref lref last post