Re: Packaging (was Re: Socket library?)
- From: Justin Cormack <justin@xxxxxxxxxxxxxxxxxxxxx>
- To: luajit@xxxxxxxxxxxxx
- Date: Thu, 4 Oct 2012 22:18:30 +0100
On 4 Oct 2012 21:56, "David Given" <dg@xxxxxxxxxxx> wrote:
>
> On 04/10/12 20:46, Simon Heath wrote:
> [...]
> > I hate to break my lurking on a rant, but... When I want to write
> > a program in a language or runtime, the first thing I do is see whether
> > that language or runtime or whatever is in Debian. If it's not, well,
> > I usually forget about it, since it's obvious that the language's
> > maintainer doesn't care about committing to supporting it as an actual
> > usable project.
>
> *raises hand* Absolutely. Me too. Using the Debian package means that I
> don't have to worry about compilation, dependencies or --- and this word
> is in bold type --- updates. Particularly since LuaJIT development is
> moving so fast; that way I can buy in to any further updates with zero
> work from me. I also don't have to worry about deploying my app, because
> I can either tell my end users to install these X packages and it'll
> Just Work, or else I can package it up myself, submit it to Debian, and
> it's even easier.
>
> I would much rather have an utterly basic LuaJIT package with a
> stdin-based REPL and no completion than not have one at all. (In fact,
> for any serious application I never use the REPL anyway, so it's largely
> irrelevant to me.)
>
> Incidentally, since LuaJIT is binary compatible with Lua, surely a
> Debian LuaJIT interpreter will Just Work with the existing Lua
> libraries? It may be necessary for any hypothetical LuaJIT Debian
> maintainer to liase with the Lua maintainer (who does a sterling job, by
> the way) to ensure the dependencies all work, but it shouldn't be hard.
>
> --
> ââââ ïïïïïïïïïïïïïï âââââ http://www.cowlark.com âââââ
> â "Of course, on a sufficiently small planet, 40 km/hr is, in fact,
> â sufficient to punt the elastic spherical cow into low orbit." ---
> â Brooks Moses on r.a.sf.c
>
I think the real issue is that there has not been a real release yet and
until then there is little point packaging. Because there are so many
changes even since the last beta it is such a moving target. Once 2.0 is
out it should be packaged up...
Justin
Other related posts:
