[Bug 815018] Review Request: nodejs - javascript fast build framework

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=815018

--- Comment #30 from T.C. Hollingsworth <tchollingsworth at gmail.com> 2012-04-29 11:57:40 EDT ---
(In reply to comment #29)
> And the spidernode project is stalled.

Stalled, but not dead apparently.  Brendan Eich said Mozilla intended to update
it to 0.6 and was very interested in providing a V8-like API to SpiderMonkey at
the last NodeConf.

> Regarding bundling, the only interaction I have seen with upstream was rather
> short, is there a effort to unbundle everything ?
> 
> I see :
> - openssl
> - zlib
> - libv8
> - npm
> - http_parser
> - libuv
> 
> Openssl, libv8, zlib are ok, they can be built with a systemwide version.
> 
> npm can be removed and use a external tarball, so there is only http_parser and
> libuv.

http_parser is already in Fedora:
https://apps.fedoraproject.org/packages/http-parser

libuv ostensibly supports being built as a shared library but last time I tried
it it FTBFS.  I haven't really had enough free time to look into what's wrong.

These two aren't a big deal anyway.  FPC would likely grant them an exception
since they have the same upstream and aren't intended to be built shared at the
moment.

> For libuv, seems all of their changes got pushed to c-ares :
> https://github.com/joyent/libuv/pull/374

Someone's sent a pull request but upstream hasn't accepted it yet.  As soon as
it is I'll gladly send them a patch to get shared c-ares working.

> So maybe this one could be unbundled quite easily.
> For libev and libeio, I didn't found much information on the web regarding
> sending patches upstream, maybe that's something we could try to do to help the
> unbundling ?

Patches can be sent to the libev mailing list (they both share the same
upstream):
http://lists.schmorp.de/mailman/listinfo/libev

Basically someone needs to send the libuv patches upstream and then update
libuv to the latest upstream version (they're several versions behind ATM) just
like was done with c-ares above.

If nobody else gets to it I'll finally have some free time to look into all
this in earnest over the summer...

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.