Skip to Content.
Sympa Menu

sm-sorcery-bugs - [SM-Sorcery-Bugs] [Bug 7751] New: TRIGGERS need to be run in a dependency sorted way.

sm-sorcery-bugs AT lists.ibiblio.org

Subject: Bugs for Sorcery are reported here

List archive

Chronological Thread  
  • From: bugzilla-daemon AT metalab.unc.edu
  • To: sm-sorcery-bugs AT lists.ibiblio.org
  • Subject: [SM-Sorcery-Bugs] [Bug 7751] New: TRIGGERS need to be run in a dependency sorted way.
  • Date: Sat, 4 Dec 2004 14:06:01 -0500

http://bugs.sourcemage.org/show_bug.cgi?id=7751

Summary: TRIGGERS need to be run in a dependency sorted way.
Product: Sorcery
Version: Devel
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: Cast
AssignedTo: sm-sorcery-bugs AT lists.ibiblio.org
ReportedBy: graphics AT sourcemage.org


I am noticing this problem during the Python 2.4 upgrade.
There are many TRIGGERS for spells which depend on Python, so they can recast
and be installed in the new /usr/lib/python-2.4 directory.
The problem appears as such: the TRIGGERS are executed in whichever
semi-random
order that cast/sorcery found them in.
The problem becomes apparent when, for example, 'straw' is cast due to its
trigger, but will fail because its dependency, 'gnome-python2' has not been
cast
yet, (and 'gnome-python2's dependency, 'pygtk2' has not been cast yet.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



  • [SM-Sorcery-Bugs] [Bug 7751] New: TRIGGERS need to be run in a dependency sorted way., bugzilla-daemon, 12/04/2004

Archive powered by MHonArc 2.6.24.

Top of Page