[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#813504: marked as done (ITP: erlang-luerl -- implementation of Lua in Erlang)



Your message dated Fri, 05 Feb 2016 14:00:20 +0000
with message-id <E1aRgvs-0005JS-BV@franck.debian.org>
and subject line Bug#813504: fixed in erlang-luerl 0.2015.12.10-1
has caused the Debian Bug report #813504,
regarding ITP: erlang-luerl -- implementation of Lua in Erlang
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
813504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813504
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Philipp Huebner <debalance@debian.org>

* Package name    : erlang-luerl
  Version         : 0.2015.12.10
  Upstream Author : Robert Virding <rvirding@gmail.com>
* URL             : https://github.com/rvirding/luerl
* License         : Apache-2.0
  Programming Lang: Erlang
  Description     : implementation of Lua in Erlang

 An experimental implementation of Lua 5.2 written solely in pure Erlang
 .
 When to use Luerl:
 .
 Fast Language Switch: Luerl should allow you to switch between Erlang and Lua
 incredibly fast, introducing a way to use very small bits of logic programmed
 in Lua, inside an Erlang application, with good performance.
 .
 Multicore: Luerl provides a way to transparently utilize multicores. The
 underlying Erlang VM takes care of the distribution.
 .
 Microprocesses: It should give you a Lua environment that allows you to
 effortlessly run tens of thousands of Lua processes in parallel, leveraging
 the famed microprocesses implementation of the Erlang VM. The empty Luerl
 State footprint will be yet smaller than the C Lua State footprint.
 .
 Forking Up: Because of the immutable nature of the Luerl VM, it becomes a
 natural operation to use the same Lua State as a starting point for multiple
 parallel calculations.
 .
 However, Luerl will generally run slower than a reasonable native Lua
 implementation. This is mainly due the emulation of mutable data on top of an
 immutable world. There is really no way around this. An alternative would be
 to implement a special Lua memory outside of the normal Erlang, but this would
 defeat the purpose of Luerl. It would instead be then more logical to connect
 to a native Lua.
 .
 Some valid use cases for Luerl are:
  * Lua code will be run only occasionally and it wouldn't be worth managing
    an extra language implementation in the application;
  * the Lua code chunks are small so the slower speed is weighed up by Luerl's
    faster interface;
  * the Lua code calculates and reads variables more than changing them;
  * the same Lua State is repeatedly used to 'fork up' as a basis for
    massively many parallel calculations, based on the same state;
  * it is easy to run multiple instances of Luerl which could better utilise
    multicores.

This package is a dependency of the next ejabberd release.

--- End Message ---
--- Begin Message ---
Source: erlang-luerl
Source-Version: 0.2015.12.10-1

We believe that the bug you reported is fixed in the latest version of
erlang-luerl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 813504@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Philipp Huebner <debalance@debian.org> (supplier of updated erlang-luerl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 02 Feb 2016 17:04:03 +0100
Source: erlang-luerl
Binary: erlang-luerl
Architecture: source amd64
Version: 0.2015.12.10-1
Distribution: unstable
Urgency: medium
Maintainer: Philipp Huebner <debalance@debian.org>
Changed-By: Philipp Huebner <debalance@debian.org>
Description:
 erlang-luerl - implementation of Lua in Erlang
Closes: 813504
Changes:
 erlang-luerl (0.2015.12.10-1) unstable; urgency=medium
 .
   * Initial release (Closes: #813504)
Checksums-Sha1:
 b9080d342d2a21b6cb0f34f4926577bc7d019afa 1995 erlang-luerl_0.2015.12.10-1.dsc
 ce50c262b600098a2473560cc634e8f9a90af7a2 85199 erlang-luerl_0.2015.12.10.orig.tar.bz2
 456d375d54ce6f3902b50cf73614f4453eae0400 2940 erlang-luerl_0.2015.12.10-1.debian.tar.xz
 b7341da78daa88cecc6cfd8d54a31a5666b1fca1 347228 erlang-luerl_0.2015.12.10-1_amd64.deb
Checksums-Sha256:
 f4539066366972fd7eb7e37e92c3d3bb0ed94c487861e0fff2be3bd036ff945c 1995 erlang-luerl_0.2015.12.10-1.dsc
 7100b7d1c618e0a86d3b5652767066a3d92d4d7f398652bb08f47d78f9df7274 85199 erlang-luerl_0.2015.12.10.orig.tar.bz2
 5fbd046ec6c3568d218bc7ca7f93f89f9ad28eb98a95c20921a1f0916ca62068 2940 erlang-luerl_0.2015.12.10-1.debian.tar.xz
 dae1ec453dbfc953f03ff3d19e38c75121460b87a3bbc745c9e688ba9ddf75c4 347228 erlang-luerl_0.2015.12.10-1_amd64.deb
Files:
 fed4216718385602fc48308e5acc1608 1995 libs optional erlang-luerl_0.2015.12.10-1.dsc
 ee73e44f2067b4d54260d1f7a8ef054f 85199 libs optional erlang-luerl_0.2015.12.10.orig.tar.bz2
 a84583c6229083f507d97e9ee8e766c4 2940 libs optional erlang-luerl_0.2015.12.10-1.debian.tar.xz
 c9bec31b335cf78c9608f5f45d33f034 347228 libs optional erlang-luerl_0.2015.12.10-1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJWsOTqAAoJEOXKjEkl5CBfG8UP/1YNPf3UnebQPPG5jkKQTta7
+Be0/tk1MxwfAzjmKYJB2cv+vPTtJj/N0qqrWPNOZyoiPO+jyfHdbrY/S1Kax3Fk
LSZQaBmvSw6g7XDvU4MfQyZZ4uNeJFgmD8aVUdQuCsInDEauLSZOTRpKTaMmURjB
fwtCjcYXZHSc9GQh8N7fihRRmMzTU5BkAlGSGDk7IQC3AD9HdHW17wMkS5Wy87yo
vMK/aHDBTTqDSddsoD0BVdZjiyZrnWRGuB8C7qvPbXM+ERukC73o3VJ8V+mIEZD7
YgnVuXJFjt9SoICdAVOyHDveSPhHskVOlQHZbV1FKMWPPAfQtygf+AGc+Tt3+fuY
FdSh0jmL0hWK01ucZmnUCdts4mX/a7NrD5RdHC2LR0EKzRjgiZH6YGWH/KIq03fs
DVWvjLcVAsJeKucygKOSo3p0aJ/Z6rbts3QZ/Bv/6O5ZzQ+qJHMjrxDTL0IL9MmB
Lc+u3Q+Zc3P3vG5BtdYKEYqrobJ/b748Vh/gzHa0M0qN0BdpZWkSyOEDR2i4/7SC
ytnM7F4JqZr+Pqa+m9+Hu96jvGvNwRdBnrkznxu27uIIj1oFY/NYrn1Y1TMqHb2c
ac8PjcBfxoPGHFRHELhXuq/aWsqNpBzzYq+QWSLcR/cQAhiCCjwY7hkPOKlZbAx1
2YFK0goGIVK921n38CvQ
=1SyX
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: