On 08/10/2016 05:29 AM, Zuzana Svetlikova wrote: > Hi, > > since nodejs currently present in EPEL is archaic and going EOL in ~7w, > it might be time to finally update it. > If anyone has any comments or suggestions, I'm all ears. > Otherwise I'll start with the update tomorrow or on Friday. >
To which version are you planning to update? I'd have a slight preference to making the move to Node.js 6.x rather than 4.x at this point, since that is going to be declared the active LTS version at the same point that the 0.10.x version goes EOL. That will mean that we get a full thirty months of support on it, vs the eighteen we will get out of Node.js 4.x. We need to consider how we're going to do this as well. We will need to figure out in advance which packages in EPEL will need to be rebuilt simultaneously (all of the native modules will) and make sure we stick them into the same Bodhi erratum. I would also recommend that we prep for this but only release the 6.x EPEL package on 2016-10-01 with the upstream release that they declare LTS, that way we have confidence we aren't shipping anything in EPEL that is going to change. (I suppose we could also start prepping it in updates-testing for a while but not allow it to go stable before that date, of course). Lastly, we should consider what to do for the future. It might be time (at least in EPEL, possibly in Fedora) to consider whether we might want to look into parallel (or at least conflicting) installation of different versions of the interpreter into releases. Given the way Node.js functions, I suspect that we could build up a mechanism to build multiple subpackages for the native modules that would run with each of the interpreters. The various versions don't necessarily need to parallel-install, but that would be ideal. (Using the alternatives system to pick which one gets /usr/bin/node and have the others be /usr/bin/node4 and /usr/bin/node6, etc.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ nodejs mailing list [email protected] https://lists.fedoraproject.org/admin/lists/[email protected]
