kapouer at melix.org
Sun Jun 5 16:52:13 UTC 2011
On 05/06/2011 18:34, Alessandro Ghedini wrote:
> Hi all,
> While updating libio-aio-perl I've noticed that both the nodejs and
> libio-aio-perl packages bundle the libeio library , and I was wondering
> if it makes sense to package it as a stand-alone package (as per Debian
> Policy §4.13) instead, like many other distributions do (Fedora, RHEL,
> OpenSUSE, ...).
> I haven't tried to build libio-aio-perl (it will need some patches,
> coordinating with upstream will be sensible) or nodejs (this seems easier)
> with the stand-alone library yet, but I think it may be worth a try.
> I've set-up an initial version of the libeio package on git.d.o at ,
> (note that I've not filed an ITP for it yet, and I won't if we decide that
> the package is not needed), and I could also take care of it in the future
> if I find a sponsor, or a DD co-maintainer.
> Any thoughts?
While i had that idea in mind when packaging nodejs, Marc Lehmann
discouraged me doing it (see the discussion below).
It was in 2009, so maybe the situation has changed.
Mon, Sep 14, 2009
J: i'm currently packaging Node  for debian,
which depends on libeio, so i'm wondering
if you plan to make a release anytime soon.
J: I started working on libeio debian package from CVS trunk,
and will make it available when i'm finished with Node packaging.
M: I don't think this is a good idea at all, but it is certainly allowed by
J: So following your advice, i'll let libeio packaged in Node...
M: I think that's by far the best thing to do, until libeio has a guranteed
stable API (it's a kind of a mess right now, mostly internally).
Debian will not like that much, as debian has for some reason enourmous
prejuduices against C (but not C++ for some reason) when embedding code
in executables, but I really think its the bets solution to guarantee
stability for you.