Nodejs and chromium both contain the V8 javascript engine (or at least some javascript engine). Add two versions of gjs for people that run gnome and we have 4 javascript engines installed on a single machine. This means two javascript engines for one browser. I think that dependency on nodejs is unjustified and could be done without.
*** Bug 610910 has been marked as a duplicate of this bug. ***
In theory, all of the packages could share one copy of V8, but the developers offer no API stability, and don't really support it as a shared library. Anyway, chromium needs nodejs to build; that's not magically going to change.
Do we know what exactly is requiring this sudden dependency change with chromium 58 and put it behind a use flag? Doubling chromium compile time seems absurd.
(In reply to Rok Kralj from comment #3) > Do we know what exactly is requiring this sudden dependency change with > chromium 58 and put it behind a use flag? See https://groups.google.com/a/chromium.org/d/msg/chromium-dev/H2IqgqwdUqs/4yOxBWIJDQAJ for some context. Without it the build fails, so it's not an optional dependency. > Doubling chromium compile time seems absurd. Do you have data do back what seems an exaggeration? These are build time results for me, as returned by qlop -t -H : chromium: 33 minutes, 41 seconds for 137 merges nodejs: 2 minutes, 5 seconds for 2 merges Also note it's not obvious what could we do at Gentoo side. Build time concerns could be valid, but they may be better directed upstream.
Just adding to this bug -- this new nodejs rdep is a showstopper for people who run libressl. Since the nodejs people are apparently uninterested in addressing libressl with or without outside contributions, I don't expect this to be fixed in nodejs anytime soon.
