Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] Lua 5.2 migration

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Vlad Glagolev <stealth AT sourcemage.org>
  • To: sm-discuss AT lists.ibiblio.org
  • Subject: Re: [SM-Discuss] Lua 5.2 migration
  • Date: Sun, 18 Dec 2011 17:21:28 +0400

On Sat Dec 17 21:56:48 EST 2011
flux <flux AT sourcemage.org> wrote:

> Why didn't you just update the lua spell in the branch instead of in
> test? That way none of the spells would have to be changed to lua51

We can't go away from 5.1 at once with one merge. lua51 spell is needed
for those who can have modules/libraries that will never work with
anything >5.1 (cause their development isn't active or so).

And it's better to update spell-by-spell migrating from Lua 5.1 to Lua
5.2, since such migration for several spells could take a lot of time
(and we can't wait for the years to have Lua 5.2 in stable for the
people). This is how it's done in Python community about 2<->3.
Developers rewrite/adapt programs to fresh 3 version. The difference is
that we can't keep Lua 5.1 and 5.2 at once in a system (transparently
at least, without modification of INSTALL_ROOT per spell).

Creation of lua52 spell logic was refused due to a simple reason also:
Lua 5.2 is newer than Lua 5.1, so by default "lua" must go for 5.2
version. Also, many among us think that the same strategy must go for
our python spell (and we should rename python3 spell to just 'python',
and create python2 spell; and yes -- it's how it's done in Arch). As
you know for the first time I was against this, but now I see it's a
better way (also recently I note that many people are trying to go with
Python 3 with theirs new projects since the beginning).

> They will also need to be instructed to do this, or we will have to add
> a lot of magic to triggers or whatever.

Yes, I'm thinking and working on this; until it's not in stable -- it's
safe to keep it as-is.

> Is there a reason you updated lua itself in test separately from in a
> branch?

The answer is simple: to let people have a new version of Lua. As we
know, branches-only strategy never worked. Proved by devel-xorg-modular,
devel-libpng branches exp, and so on (and will never work like
Ladislav said many times).

--
Dont wait to die to find paradise...
--
Cheerz,
Vlad "Stealth" Glagolev

Attachment: pgp_WyPryUd_h.pgp
Description: PGP signature




Archive powered by MHonArc 2.6.24.

Top of Page