Skip to Content.
Sympa Menu

sm-commit - Re: [SM-Commit] GIT changes to master grimoire by Remko van der Vossen (001758c5753fae25ad647fa9492165e489fd7263)

sm-commit AT lists.ibiblio.org

Subject: Source Mage code commit list

List archive

Chronological Thread  
  • From: Ismael Luceno <ismael AT iodev.co.uk>
  • To: Remko van der Vossen <wich AT sourcemage.org>
  • Cc: sm-commit AT lists.ibiblio.org
  • Subject: Re: [SM-Commit] GIT changes to master grimoire by Remko van der Vossen (001758c5753fae25ad647fa9492165e489fd7263)
  • Date: Mon, 6 May 2019 16:36:47 +0200

On 06/May/2019 14:15, Remko van der Vossen wrote:
<...>
> Yes, the problem is indeed that we cannot assume that people have a
> recent sorcery. Especially since stable is ancient and even the devel
> version is some version from 2017 that doesn't contain many of the fixes
> that you have done in the recent past.
>
> I believe what we used to do is get whatever functionality into sorcery
> and release a stable version of sorcery containing that feature, then
> wait a certain length of time (year or something?) before we assumed it
> to be generally available for use in the grimoires. Problem is that the
> cleanup of all workarounds and hacks was never orchestrated well, so we
> have a lot of cruft hanging about all over the place.
>
> Do we have any sensible way to make a sorcery upgrade mandatory? What we
> could do is actually check for a minimum sorcery version in the spell
> that needs a specific feature. That could be provided in a grimoire
> function. Of course then we need some easy to use overview of which
> features are available in which versions of sorcery.

Well, nowadays the FUNCTIONS files are mandatory (things break badly
without USE_FUNCTIONS=on), so we could add the version test at the
begining of the grimoire's FUNCTIONS.




Archive powered by MHonArc 2.6.24.

Top of Page