Bugs for Sorcery are reported here

[bugzilla-daemon AT metalab.unc.edu]

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





------- Additional Comments From acedit AT armory.com  2004-06-17 19:26 -------
Seth you are exactly right, the decision to put the file in /tmp is based
on the fact that we should not needlessly clutter a users system and that
we have no other means to take care of removing the file other than carrying
the extra baggage of a hack around /forever/.

Had we had the foresight to get upgrade hooks installed into sorcery
before pushing full depends into stable we could have had a hook that
ran cleanse on an upgrade from the old stable to the new stable rather
than this this admittedly hacky hacked up hack (which is a hack, btw in
case we forgot).

Let me also refer the alternative: without running cleanse and having a
thoroughly screwed up depends tree cast will crap out, as we all know.
This is why Paul wrote cleanse, to fix this. However we can't assume everyone
is in tune with everything and therefore will implicitly know that cleanse
needs to be run when cast craps out. SO we are left with either letting
all our users upgrade to the new stable to find that cast craps up
mysteriously (hardly instilling in them the belief that its stable at all)
or we stick a marginally annoying message in their face. The message was
intended to be marginally annoying and save the user from the even more
annoying fate of cast crapping out on a messed up depends tree. I would
rather have users stuck with an annoying message in cast than to have them
lose even more faith in stable sorcery being stable (lets not forget our
nightmarish series of bad stable releases).

SO yes, we faced a dilemma, there was no feasable "right" solution. So
we weighed the options and took the one that seemed most reasonable.
I posted to the list about what we were doing, no one responded (to
my knowledge or recolection). No one has come up with a convincing
argument to use something other than /tmp other than "its annoying",
furthermore no one on the anti-/tmp side has addressed the persistence
issue. We're all grown up here, at least I thought, so we should be
capable of providing a reasonable argument rather than avoiding the
reasons for the decision and saying its annoying over and over again.

I even went so far as to provide a half-baked workaround to make the
warnings go away for those of us who can't seem to comprehend the
alternatives to not having this stupid broken hack to begin with. I asked
Paul to request for comments before closing the bug and waited over a week
for a response, none was given. Finally I requested comments one more time
and what do I get? "its annoying", yes we know, you said that before, why
don't you read my comment and use the workaround, or at least give some
indication why that's not going to make you happy. Finally, yes I'm
probably an over-extended stressed team lead, so why dont you work with
me on this one rather than telling me that the decision i've made and
fought day and night in the trenches explaining to users (and explaining
the alternatives of) is annoying? I struggled with this and I'm sorry
its annoying, and Im sorry I got annoyed back but perhaps now you'll
know where Im coming from.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.