Skip to Content.
Sympa Menu

sm-sorcery-bugs - [SM-Sorcery-Bugs] [Bug 5649] stable sorcery's dispel no longer removes initscripts when a spell is removed

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 5649] stable sorcery's dispel no longer removes initscripts when a spell is removed
  • Date: Thu, 5 Feb 2004 13:49:54 -0500

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





------- Additional Comments From charkins AT pobox.com 2004-02-05 13:49 -------
I don't want to get in the middle of a flameware here, so lets get the pros
and
cons of this out in the open so we can make an informed decision one way or
the
other.

Having these tracked by sorcery makes it easy to replicate an installed spell
into another environment. I relied on this behavior in creating my binery
system
for using a single smgl machine to install a number of binary-based smgl
machines. This obviously isn't (and shouldn't) be a concern of the sorcery
team,
but I think the root problem should be a concern. One of the goals of the iso
was to selectively install spells from their source cache's rather than use
one
big honking image.tar.bz2. Without tracking these scripts in sorcery, init
scripts will need some sort of special handling.

I still don't see any reason why tracking these is a problem. They'll only get
removed if the spell is dispelled. If the spell is dispelled, then there
should
be no need for the init script.

Now, if this behavior is going to stay, then the installer should "telinit
disable pcmcia-cs" in addition to dispelling it.



------- 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