Public SourceMage Discussion List

[Sukneet Basuta <sukneet AT gmail.com>]

On Wed, Aug 27, 2014 at 2:29 AM, Thomas Orgis <thomas-forum AT orgis.org> wrote:

Well, that says it all. We only have choices of "bad" things, due to
reality constraints. I then opt for the bad thing that makes it
possible to have a current working system with quite some mess during
upgrade instead of the thing that lets Source Mage die.

So, what would be the dirty approach to get this done from your
experience?

I've attached what I posted close to a year ago. Javier also had the idea of chaining a planar list of casts, which maybe a better solution than trying to rely on UP_TRIGGERS.

---------- Forwarded message ----------
From: Sukneet Basuta <sukneet AT gmail.com>
Date: Fri, Nov 8, 2013 at 8:29 PM
Subject: Re: [SM-Discuss] devel-xorg-modular security fixes
To: SM-Discuss <sm-discuss AT lists.ibiblio.org>

I haven't had the the time to work on this in over 2 months, so I'm giving up on it. I've attached a git patch that adds a bunch of spells to libpthread-stubs' UP_TRIGGERS that should get a working system at least. However, the problem is that I can't get the spells to cast in the correct order (adding dependencies ends up with cyclical dependencies). So you have to keep recasting libpthread-stubs until everything compiles okay. This is not a proper upgrade path imo, but I couldn't think of anything better given the current limitations of Sorcery.

This isn't a complete list either since I gave up adding spells to it after a bit and instead focused on trying to get spells to cast in the correct order. If the leads decide to merge this, I'll try to eventually compile a complete list of spells that need recasting.

Attachment: 0001-libpthread-stubs-added-a-bunch-of-spells.patch
Description: Binary data