Skip to Content.
Sympa Menu

sm-sorcery-bugs - [SM-Sorcery-Bugs] [Bug 16100] [PATCH] first proof of concept for protecting files from installed spell version

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 16100] [PATCH] first proof of concept for protecting files from installed spell version
  • Date: Wed, 18 Mar 2020 12:33:42 +0000

Comment # 9 on bug 16100 from
It just occured to me … wouldn't it actually work to _not_ dispel files
before install, so that stuff that is overwritten is overwritten, but
things like old SOVERSIONS of libs are still there?

The spells that should have been dispelled are recorded. Then, a cleanse
operation picks up on that and removes the files that have not been
overwritten by the new version (or another spell altogether), on the
mage's request.

This would be a simple list of undead spells, and possibly some hints on
which spell replaced them to speed up the check that an unchanged file
(md5sum) might be adopted by a different spell. Cleanse would also have
a mode to check if any spell uses libraries belonging to an undead spell
and try to re-cast to update it. Then, undead spells can be safely
dispelled. Of course, that needs to be a smart dispel that only deletes
files that still belong to the undead spell. I guess we could modify
the spell's install file after the cast that now would trigger dispel.

Is the idea sufficiently described? Someone agree, violently disagree?

I still think it is worth it to maybe independently preserve old SOVERSIONS for 
the case of user software still relying on the old ABI, though. Maybe that
can be combined and managed by sorcery.


You are receiving this mail because:
  • You are the assignee for the bug.



Archive powered by MHonArc 2.6.24.

Top of Page