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: Sun, 8 Sep 2002 21:52:39 -0500

Too bad we are gonna have to go back and fix it to work right now.

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

-Ryan

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

There has to be a version which "means something" for users to
keep track of what they are using.

And what is being asked from the people who want one spell (myself included),
is that:

1. One sorcery spell
2. Two products available from this spell (stable or devel)
3. No updating of the spell needs to be done for new versions to
be installed.

Some of us also are very certain that (myself included):

4. There must be a way of knowing which version you have installed
(i.e. 0.8.1 for stable, or 20020909 for devel)


The fact is, that this simply cannot be easily done without changing
the way spells work fundamentaly.

1 & 2: Spells are not meant to work like this, you do not dynamically
change what is being installed based on some CONFIGURE question or
parsing and doing a search&replace on some value in the DETAILS file.
It's a hack, messy, and will create problems (as we have seen).
VERSIONS get totally screwed up.

3: This is sort of possible, with the LIFESPAN option in the DETAILS
file, but breaks 1,2 and 4


We aren't getting anywhere talking this over, and something needs to be
done. In theory, allot has been suggested to get all of these things
to work together, but I haven't seen any real solutions, and I am
not up for rewriting several sorcery libraries and commands to try
to hack in The Right Way to do this. It would probably cause trouble
with every other spell in the grimoire too.

I'm just going to make a sorcery-stable and sorcery-devel spell, they
both provide 'sorcery', so conflict. The devel spell will not need
to be updated (version will just be the date it was installed). However
the stable spell will need to be updated everytime a new release is
made.

- nick
_______________________________________________
SM-Sorcery mailing list
SM-Sorcery AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/sm-sorcery





Archive powered by MHonArc 2.6.24.

Top of Page