sm-sorcery-bugs AT lists.ibiblio.org
Subject: Bugs for Sorcery are reported here
List archive
[SM-Sorcery-Bugs] [Bug 10186] Prompt to remove spells if user declines casting all
- From: bugzilla-daemon AT bugs.sourcemage.org
- To: sm-sorcery-bugs AT lists.ibiblio.org
- Subject: [SM-Sorcery-Bugs] [Bug 10186] Prompt to remove spells if user declines casting all
- Date: 9 Dec 2005 03:43:09 -0000
http://bugs.sourcemage.org/show_bug.cgi?id=10186
acedit AT armory.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|Cast |depends
------- Additional Comments From acedit AT armory.com 2005-12-08 21:43 -------
cast used to do this like 3 years ago, but it didnt work well, and since then
our dependency system has gotten a lot more complex. Mending the dependency
tree
like that is non-trivial to say the least. It looks simple, but it really is
not.
Also, you're given the opportunity to edit the queue during a system-update as
well as from the command line via sorcery queue, sorcery review-queue, sorcery
remove-queue, or with your editor before you do cast --queue.
Most of the time you're not casting from the queue, so Im not sure what there
would be to gain for such a limited option. Incidentally cast --queue is just
cast -c $(cat $QUEUE). Im assuming you're saying anything from the queue can
be
safely removed because you are infering that anything from the queue is a root
node, and anything new must be a leaf. And thus anything from the queue is
safe
to just pluck off because its a root node (not always true), and its installed
already (bad assumption, the queue can be used for other things).
I'd like to resolve this as wontfix since I think the user has plenty of
opportunity to remove stuff from the queue before running cast --queue and
sorcery rememebers all the answers from aborted depends processing and uses
them
as the default next time so you dont loose a whole lot by hitting ctrl-c,
modifying the queue and trying again.
I can ellaborate on the un-feasability of trying to modify the dependency tree
as post-processing if you'd like. I'm certainly not saying its impossible, its
just a lot of work, bug-prone due to a huge number of corner cases, and
probably
wouldn't bring much benefit. I think an overly simple approach would be so
broken or restrictive it would be practically useless.
--
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.
-
[SM-Sorcery-Bugs] [Bug 10186] Prompt to remove spells if user declines casting all,
bugzilla-daemon, 12/08/2005
- <Possible follow-up(s)>
- [SM-Sorcery-Bugs] [Bug 10186] Prompt to remove spells if user declines casting all, bugzilla-daemon, 12/09/2005
- [SM-Sorcery-Bugs] [Bug 10186] Prompt to remove spells if user declines casting all, bugzilla-daemon, 12/11/2005
Archive powered by MHonArc 2.6.24.