2009/3/19 Nicolas Cannasse <[email protected]>:
>
> Yes, it's a bit difficult I think to adapt libneko to Debian standards. In
> particular, it's been designed to be system-agnostic, so for instance all
> additional libraries apart from libneko itself are .ndll files and not .so
> files. This also prevent any kind of versioning since these NDLL are loaded
> by libneko and it would then mean modifying the neko system to match the
> Debian versioning scheme which I'm not sure I want to do ATM.
>
OK. I will then try to keep my own versioning libneko.so so that it
can be used as a shared library by people who wants to embed the Neko
VM. The NDLLs will live together separately, depending on libneko. I
have already create an upload with this design; the layout is like
this:
libneko0
------------
/usr/lib/libneko.so.0.0
/usr/lib/libneko.so.0 -> libneko.so.0.0
neko-dev
------------
/usr/include/neko*.h
/usr/lib/libneko.so -> libneko.so.0.0
neko
------------
/usr/lib/neko/*.ndll
/usr/bin/neko*
Cheers,
/JP
--
Jens Peter Secher.
_DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_.
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
