Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] Improved Sorcery Trigger Support

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Eric Sandall <eric AT sandall.us>
  • To: Andrew <afrayedknot AT thefrayedknot.armory.com>
  • Cc: sm-discuss AT lists.ibiblio.org
  • Subject: Re: [SM-Discuss] Improved Sorcery Trigger Support
  • Date: Mon, 5 Sep 2005 14:07:28 -0700 (PDT)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, 3 Sep 2005, Andrew wrote:
Hi, given the recent concerns over the openssl update I decided
to go ahead and implement the solution I outlined below in devel
sorcery. Disclaimer: this is in the "proof of concept" phase, its not
completely ironed out, Im adding it so other interested parties can try it
out and we can iterate on improvements if need be (bazaar style). Swoolley
is going to update the openssl spell in test grimoire to try this out.

Awesome, thanks! :)

from the spell maintainers perspective you add a file called "UP_TRIGGERS"
(for lack of a better name), in it you call a function called "up_trigger"
for each spell thats going to break due to an abi change (or whatever).

Heres a brief example:
for each in $(gaze depends $SPELL 1|cut -f1 -d:); do
up_trigger $each cast_self
done

How does it determine an ABI/API change? (note I have not RTFC)

This is almost exactly the same as placing a TRIGGERS file in each of
the spells that depend on openssl, but hopefully easier.

Is there a reason we're adding another file instead of using the
TRIGGERS file for this?

from the users perspective the following will happen: all the spells
that depend on openssl (in this case) will automatically get added to
the list of spells to cast. Hopefully after cast completes there wont
be any spells broken due to ssl update; thats the goal at least.

Only if the (e.g.) openssl ABI changed, not on every update, correct?
Or is this just on all version changes? The last is still better than
every cast and is probably much easier/cleaner to do than to figure
out ABI/API changes for every library.

- -sandalle

PS: Just got back from a somewhat long weekend, so I'm a bit addled.
;) Please ignore any idiotic comments, or feel free to let me know
they are idiotic. =)

- --
Eric Sandall | Source Mage GNU/Linux Developer
eric AT sandall.us | http://www.sourcemage.org/
http://eric.sandall.us/ | SysAdmin @ Inst. Shock Physics @ WSU
http://counter.li.org/ #196285 | http://www.shock.wsu.edu/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDHLOSHXt9dKjv3WERAm+uAJ9ZQZ45UCY6JU/IG9sKMO6IhjEkIwCfZRXw
H/ieU+/YO5RHE2/BZqlgISo=
=nsfi
-----END PGP SIGNATURE-----




Archive powered by MHonArc 2.6.24.

Top of Page