Skip to Content.
Sympa Menu

sm-sorcery-bugs - [SM-Sorcery-Bugs] [Bug 8333] New: support for multiple versions within a spell

sm-sorcery-bugs AT lists.ibiblio.org

Subject: Bugs for Sorcery are reported here

List archive

Chronological Thread  
  • From: bugzilla-daemon AT bugs.sourcemage.org
  • To: sm-sorcery-bugs AT lists.ibiblio.org
  • Subject: [SM-Sorcery-Bugs] [Bug 8333] New: support for multiple versions within a spell
  • Date: Tue, 1 Mar 2005 01:34:35 -0800 (PST)

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

Summary: support for multiple versions within a spell
Product: Sorcery
Version: Untargetted future release
Platform: Other
URL: http://wiki.sourcemage.org/index.php?page=Versioning
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: subroutines
AssignedTo: eric AT sandall.us
ReportedBy: acedit AT armory.com
CC: sm-sorcery-bugs AT lists.ibiblio.org


This bug is for tracking the spell versioning project. Here are some issues
within sorcery that I think will need to be addressed for this project.

* spells installing files sanely (this could be accomplished in part with
grimoire libraries)
* build api 3 may or may not need to be invoked depending on the scheme used
above
* cast will need to have some way of knowing if its supposed to dispel the
current version(s) of the spell or not, this may or may not be something you
do
with cmd line args. Just something to think about for now.
* must have a naming convention such that libcodex can find these spells
$spell/$version has been suggested where $version is an actual sub-directory
* another variable, in addition to
SCRIPT_DIRECTORY/SECTION_DIRECTORY/GRIMOIRE,
may need to be defined for $SCRIPT_DIRECTORY/$VERSION
* codex.index or some other index must be generated so the sub-spells can be
found
* code for providex.index may need updating
* libtablet will need updating to access the subspell files
* libtablets code to source a spell will need updating, tablet itself should
be
content with multiple versions of a spell installed however.
* libstate, depending on the naming scheme used some of these functions may
need
to be updating to deal with duplicate versions of the spell
* what will entries in /var/state/sorcery/packages and depends look like?
* if the spellname is $spell/$version then the logfile naming will have to
pick
the actual spell name out so the filename doesnt include a /, not a big deal,
just something to think about
* libdepends may need some updating
* all the run_<spell_file> functions will need to be updated to follow
whatever
inheritence scheme is decided upon

Theres probably other things that need to be looked at, but thats all I can
think of for now. Let me know if you need any help or clarification on the
points above, i'll gladly guide you through the twisty maze of passages in
sorcery (all different), you know where to find me :-)

I think the project is going to work out of the proj4 branch, if you think
this
can be done in the 1.13 or 1.14 timeframe we can retarget.

--
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



  • [SM-Sorcery-Bugs] [Bug 8333] New: support for multiple versions within a spell, bugzilla-daemon, 03/01/2005

Archive powered by MHonArc 2.6.24.

Top of Page