Skip to Content.
Sympa Menu

sm-sorcery-bugs - [SM-Sorcery-Bugs] [Bug 8465] dispel spell totally

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 8465] dispel spell totally
  • Date: Mon, 28 Mar 2005 11:23:17 -0800 (PST)

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





------- Additional Comments From acedit AT armory.com 2005-03-28 11:23 -------
The first problem with this is spells must track all these files, sorcery cant
dispel the database file if its not tracked, it also cant remove config files
the user creates. This is much more feasable with our new spell level
volatiles
and configs filters. The spells that arent tracking these things should be
fixed
to do so. Or clean them up in POST_REMOVE.

Accounts are currently managed completely out of band from sorcery, sorcery
has
no idea accounts exist, and I think its going to stay that way. So spells
should
clean that up in POST_REMOVE, and bugs should be filed against spells that are
not doing that, or at least, dont have options to do that.

On the sorcery end, one option would be to set a magic variable like SCRUB to
'on' in this case, then POST_REMOVE can check it and do more in-depth removal
(like account removes, removes of database files and other un-tracked things).
Id rather do that than have a new, mostly redundant file.

For sorcery this issue boils down to a policy adjustment for removing config
files (those matched by /var/lib/sorcery/configs, and a spell level
equivalent.
We remove all files not matched by system and spell level config filters, and
unmodified config files unconditionally. Modified configs are treated
differently, either they're left as is, or renamed with a date extension. In
other words, this change would modify the behavior to remove those files as
well.

The crux of this work on the sorcery side would be to add a command line flag
which sets the SCRUB variable, then perform a different action on modified
config files. Thats it.

There is far greater work on the grimoire side to 1) get more files tracked
and/or 2) do a better job removing files (depending on the value of $SCRUB).
Since the SCRUB flag wont be in stable sorcery anytime soon the spells could
easily use the query function instead with a logical OR of the $SCRUB flag.

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




Archive powered by MHonArc 2.6.24.

Top of Page