2009/7/31 Nicolas Cannasse <[email protected]>:
> Michael Pliskin a écrit :
>>
>> Echoing Jens's comment: it'd be nice to have more traditional and
>> OS-friendly way to install neko and its components. We should have rpm and
>> debian packages I believe. We have them already for Fedora and Debian
>> (correct?),
There certainly are packages for Debian, see
http://packages.debian.org/neko
http://packages.debian.org/haxe
and for backports-in-preparation (which should also make it easier for
Ubuntu users)
http://people.debian.org/~jps
>> but tora is missing there, so I vote for it to be added more or
>> less the way Jens suggests. Haxelib is great for development, but no so nice
>> for configuring the production servers: for instance, when there is a
>> security fix for mysql client applied, you normally want to propagate that
>> into neko-mysql which requires a rpm/debian package with dependencies and
>> all of it, and haxelib is not of much help here.
>
> I'll let the package maintainers decide on this one, I don't have a strong
> religious thinking about how tora should be distributed ;)
OK, thanks. However, I do not think I have the time myself right now
to find a good solution for how to include the full Tora in the Debian
package (I am not using Tora myself).
But maybe others have ideas? The Mercurial repositories for the
packages are here:
http://hg.debian.org/hg/collab-maint/neko/neko
http://hg.debian.org/hg/collab-maint/haxe/haxe
Especially the debian/patches directories can be of interest because
these directories contain my patches to the original source.
If you are interested or need help with some Debian packaging magic,
just drop me a line!
Cheers,
--
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?
--
Neko : One VM to run them all
(http://nekovm.org)
