Package: liblua5.1-0-dev Version: 5.1.4-5 Severity: wishlist Hi, I'm the maintainer of Enigma, which currently ships an own copy of Lua. As far as I know (from discussion with upstream and on #debian-devel) it is currently impossible for me to re-use the Debian lua packages for building Enigma. The main reason is that C++ exceptions and lua compiled for C use will break badly.
Quoting from the LUA unofficial FAQs: By default if lua 5.1 or later is compiled as C++, it will use C++ exceptions to unwind the stack rather than longjmp/setjmp, though this is configurable (at compile time). See luaconf.h near LUAI_THROW/LUAI_TRY for a discussion of this. As far as I know, Enigma Lua also comes with some patches that e.g. add an assertion facility that isn't yet in main lua. Still another lua user in #debian-devel expressed the wish that there were a C++-built lua version in Debian to re-use in his own projects. Enigma also uses "tolua++" instead of "tolua". from http://www.codenix.com/~tolua/ I am aware that lua upstream considers embedding a custom lua version in the application the proper way instead of using a shared library, and I do not want to reopen this discussion. The debian policy usually is to avoid duplicated code to make security maintenance easier. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-rc8-686 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages liblua5.1-0-dev depends on: ii libc6-dev [libc-dev] 2.10.2-2 GNU C Library: Development Librari ii liblua5.1-0 5.1.4-5 Simple, extensible, embeddable pro ii libreadline-dev 6.0-5 GNU readline and history libraries Versions of packages liblua5.1-0-dev recommends: ii libtool 2.2.6a-4 Generic library support script ii pkg-config 0.22-1 manage compile and link flags for liblua5.1-0-dev suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
