On 08/10/2016 10:02 AM, Zuzana Svetlikova wrote:
I originally planned updating to v4, however, 6.x seems like a good
idea.
So, multiple errata for nodejs/native modules/npm, or one to rule them all?
There is ~700 nodejs packages in EPEL and I don't really know, if the rest are
dependencies of some bigger application or just random modules.
We don't need to rebuild all the packages, just the ones that have a requirement
on nodejs(v8-abi), I think.
Looking through a repoquery on Fedora (which has a lot more packages), we don't
have any packages that explicitly don't work with v6, either)
```
dnf repoquery --whatrequires "nodejs(engine)" --requires \
| sort -u \
|grep "nodejs(engine)"
```
I can imagine having two versions in Fedora (although I can't
really see the use
case), but having two node interpreters in EPEL means that one eventually goes EOL.
Honestly, I think the reverse makes more sense. Fedora should only have a single
version for each release, but EPEL should probably always carry both supported
LTS releases if we can manage it. It will provide people with an opportunity to
migrate on their own schedule. I don't love that we're forcing the 0.10.x ->
6.x
jump here, but 0.10.x is going EOL, so we don't have a lot of choices.