[Bug 732552] Review Request: nodejs - Evented I/O for V8 JavaScript

[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=732552

T.C. Hollingsworth <tchollingsworth at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
             Blocks|177841(FE-NEEDSPONSOR)      |
         Resolution|                            |WONTFIX
               Flag|needinfo?(wm161 at wm161.net)  |
        Last Closed|                            |2011-10-24 18:58:22

--- Comment #31 from T.C. Hollingsworth <tchollingsworth at gmail.com> 2011-10-24 18:58:22 EDT ---
Per our discussion via e-mail, I'm going to ship Node.js in a third-party
repository [1] for the time being, until such time that the bundled library
problems can be patched or upstream decides they're worth working out:

>The big issue right now is bundled library madness.  It gets a lot
worse with 0.5, where upstream moved the ev/eio stuff into its own
library (libuv) that abstracts that out so Windows support can be
added.  That library is presently a spaghetti of bundled libraries
with just enough minor changes to make it unreasonably difficult to
split them out.  I'm hesitant to bother with a working 0.4 if 0.6
(which is due to be released pretty soon now) is never going to be
acceptable for Fedora.

>I fear the only way it might make it into Fedora is for FPC to decide
they've modified it enough to grant an exception, but that seems
unlikely (since this is pretty much the same situation Chromium is
in).  It might be wiser to just maintain it in a third-party
repository for the moment.

In the meantime, I'm closing out all my Node.js-related review requests.

[1] http://nodejs.tchol.org/

-- 
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.