[2864] in Release_7.7_team
Re: rpmupdate upgrade and exception lists
daemon@ATHENA.MIT.EDU (andrew m. boardman)
Tue Jul 24 23:02:35 2001
Date: Tue, 24 Jul 2001 22:57:55 -0400
Message-Id: <200107250257.WAA30606@pothole.mit.edu>
From: "andrew m. boardman" <amb@MIT.EDU>
To: ghudson@MIT.EDU
CC: jweiss@MIT.EDU, release-team@MIT.EDU
In-reply-to: <200107250035.UAA07396@egyptian-gods.MIT.EDU> (message from Greg
Hudson on Tue, 24 Jul 2001 20:35:11 -0400)
[moved to release-team]
>> Is it you're plan that rel-eng will download all security related
>> rpm upgrades from RH, and put them in either the regular rpmlist for
>> the next patch release (if it's something we install by default) or
>> the update-only list if it isn't (and that there would be a seperate
>> update only list for each patch release)?
Not to speak for Greg, but I've been thinking about an identical
mechanism for a while, since security updates of random packages are at
the core of the whole 'Minimal Athena' idea that keeps being mumbled
about, that's about the best approach anyone has come up with. (Random
updates *are* going to break things, so about all we can do is decrease
the set of random breakage we're going to inflict on users as much as
possible.)
>I figured Andrew would do some of this work, but that's the general
>idea.
Yeah, I was expecting to. I vaguely expect that we'll need a whole
separate release mechanism, although it needen't be as involved as the
Athena release system, since we explicitly don't care if we break things.
Or so the theory goes...
