Public SourceMage Discussion List

[Seth Alan Woolley <seth AT positivism.org>]

On Wed, May 04, 2005 at 07:20:34AM +0200, Arwed von Merkatz wrote:
> On Tue, May 03, 2005 at 03:28:46PM -0700, Seth Alan Woolley wrote:
> [...]
> > > What about a _single_ update that needs recompiles of dependent spells?
> > > Triggers don't help here as those spells can't know about that recompile
> > > dependency before it happens. It's something cleanse --fix usually
> > > catches nicely, but I want a way for gurus to document that so the QA
> > > team can put it in the release notes of the stable grimoire.
> > 
> > Nothing QA team does in the grimoires can do anything about this libmpeg2 
> > example without some sort of trigger.
> > 
> > Because putting abi-new-libmpeg2 into stable will break all spells 
> > unless all libmpeg2-dependent spells have a version update as well (We 
> > could increment UPDATED on all dependent spells at the same time 
> > libmpeg2 is integrated to stable, I suppose) as the system update 
> > process should guarantee dependency-aware compile order, but only if all 
> > spells were compiled at that system update.
> > 
> > Won't a cleanse --fix find the abi update since whenever you do an abi 
> > update you're supposed to increment the library version number, right?
> > 
> > I'm wondering just exactly what you want done for test -> stable 
> > integration, and then maybe I can integrate it into a policy document in 
> > this case.
> 
> cleanse --fix will find those issues. What I'd like is a way to document
> such things somewhere so users of the stable grimoire can check before
> they update whether the update will probably require a longish cleanse
> run or not.

There's a grimoire history changelog for important things like this, I 
would think.  Also the review queue stuff would have that kind of 
information for more obscure spells as well.  If that doesn't work, we 
can always have a wiki'd release notes page built up during stable-rc 
cooking.

Seth

-- 
Seth Alan Woolley [seth at positivism.org], SPAM/UCE is unauthorized
Key id 00BA3AF3 = 8BE0 A72E A47E A92A 0737  F2FF 7A3F 6D3C 00BA 3AF3
Quality Assurance Team Leader; Security Team Member, Leader Emeritus
Linux so advanced, it may as well be magic http://www.sourcemage.org
Elected Coordinating Committee Member, Secretary, and Finances Chair
Pacific Green Party of Oregon - Peace - http://www.pacificgreens.org

Attachment: pgp8wSantLC6O.pgp
Description: PGP signature