Skip to Content.
Sympa Menu

sm-sorcery - Re: [SM-Sorcery]sorcery: stable/devel spells

sm-sorcery AT lists.ibiblio.org

Subject: Discussion of Sorcery related topics

List archive

Chronological Thread  
  • From: Ryan Abrams <rabrams AT sourcemage.org>
  • To: Nick Jennings <nkj AT namodn.com>
  • Cc: sm-sorcery AT lists.ibiblio.org
  • Subject: Re: [SM-Sorcery]sorcery: stable/devel spells
  • Date: Mon, 9 Sep 2002 07:11:00 -0500

Nick,

Like I said, I may be, and probably am wrong. But I think the idea of a single spell is valuable enough that I am going to spend some time proving that to myself. I am not trying to discount your evaluation of the situation. I am just saying that I think there is a way to make it work (though it may be a crazy hack in the spell)

I think Nathan's suggestion is a good one in fact, though it may not fix everything.

Don't worry, I will not overwrite your work. If you have something working, I won't break it unless i have something better tested, working, and discussed among the group /after/ it's written. In the meantime, I will save it as something like "sorcery-new" or some such.

I just am not thrilled about all our users switching from sorcery to sorcery-X and back again, simply because we couldn't find a way to fix the sorcery spell in the first place.

-Ryan


On Sunday, September 8, 2002, at 11:08 PM, Nick Jennings wrote:

On Sun, Sep 08, 2002 at 09:52:39PM -0500, Ryan Abrams wrote:
Honestly, I don't buy the version bug argument for doing this. The
version of sorcery that is installed should /not/ be defined by the
spell.

Well, sorry to break it to you Ryan, but that /is/ the way version
is defined in spells. I've never really liked it (often spells break
simply because the version needs to be bumped). But that is the way it
is right now.

Thats sort of the point. Sorcery should have a hardcoded version
variable, which it uses to judge what is installed. Thus there is no
chance of the version being confused. whatever is installed is
installed.

I don't know what you mean really, but the VERSION variable is
in the DETAILS file, that is what is used when adding an entry in
the installed packages file for the spell. Everything else uses
that value.

I realize that normally spells define versions. This is not a case
where that should happens. I think we can justify the exception for
sorcery.

I do think things should change, I do not think we can justify the
exception for only sorcery. In which case it wouldn't be an exception
but rather a form of spell. Many spells could benefit from the ability
to track different branches of the same application. (Take mozilla
for instance).

I absolutely do not agree with "making an exception" for sorcery and
hacking the code to do things differently for this one single spell.
It's messy, and could cause lots of problems (which we've already
experienced from this so far).

I haven't yet seen a good explanation as to why the various solutions
that have been suggested wont work. so, to learn, i will put my
projects on hold, go back, and try them. I still think this is a
relatively easy thing to do. I will likely be proven wrong when i try
to do it. But i am gonna give it a go anyway. Cause i am stubborn like
that, and honestly, the value of a single sorcery spell makes it worth
the attempt.

Go for it Ryan, but please don't over-write my work until your method
has been proven to work.

I also think you need to clarify what you mean by "version" you are
using it interchangeable between VERSION (i.e. 0.8.1) and BRANCH
(i.e. stable/devel). See bug #917 also.

--
Nick Jennings
Sorcery Team Lead





Archive powered by MHonArc 2.6.24.

Top of Page