[1888] in SIPB_Linux_Development
Re: 4.2 package scheme
daemon@ATHENA.MIT.EDU (Salvatore Valente)
Sun Nov 9 05:45:43 1997
Date: Sun, 9 Nov 1997 05:45:14 -0500
To: linux-dev@MIT.EDU
In-Reply-To: "[1815] in SIPB_Linux_Development"
From: Salvatore Valente <svalente@MIT.EDU>
Hi. I wrote:
I've written a description of how I think package upgrading should
work. It's in /mit/linux/devel/sals-scheme/README...
It suggests a new script, "makepackage"...
It allows for packages to be upgraded separately.
I finally wrote makepackage. To celebrate this momentous occasion,
I've rearraged /mit/linux/packages a bit.
/mit/linux/packages/README is the README file from my previous email.
It describes makepackage and the packaging scheme in general.
/mit/linux/packages/current/, as described in the README file, contains
a full set of spec files and rpm files built by makepackage.
There are some small aesthetic difference between the rpm files I just
created and the ones currently in RH-Athena 4.2.
- I think that "1.0.A7.7.3" is an annoyingly long version number, so I
built the packages with the version number "7.7.3".
- For software that has a real version number, I used just the
software's version number. For example, RH-Athena currently comes
with "mh-6.8.0.A7.7.3". My package is "mh-6.8.0".
- Since makepackage created all new .spec files, each rpm was created
as revision 1. This was unintentional. If I had thought about it, I
would probably have used a higher revision number than whatever was
last used by Aaron's mkallspecs script. However, I don't think it's a
big deal, since the packages all have new version numbers anyway.
So, we now have the ability to update single packages. Let's release
this puppy.
Have a nice day.
-Sal.
