NodeJS needs two slots for the 1.x version and the 4.x version. It has made a jump from 1.x straight to 4.x. As a developer, sometimes I need to use both 1.x and 4.x versions, they are very different in language capabilities.
(In reply to ArticIce(Juice) from comment #0) > NodeJS needs two slots for the 1.x version and the 4.x version. It has made > a jump from 1.x straight to 4.x. > > As a developer, sometimes I need to use both 1.x and 4.x versions, they are > very different in language capabilities. 1.x isn't supported upstream which makes it hard for us to support it. Our ambition is to treat the LTS branch as 'stable', currently 4.x. Once 6.x will make the switch later this year, we will also make this transition. This doesn't mean we will invalidate older ebuilds right away, but as older versions grow unsupported we need to take security issues into consideration. If you insist on using unsupported upstream versions I suggest you make an overlay and maintain it. If others are interested in this I bet there could be a joint effort to maintain backports of security patches, but seeing how v8 doesn't even backport security patches you will have a pretty significant task doing so. I hope you understand our reasoning following upstream in terms of availability!
Well, ok, now I need slots for 4.6, 6 and 7 versions. Am I really the only one who needs it? Are others using "node version switcher" and binaries?
Closing this due to lack of activity so far and it being highly non-trivial to slot NodeJS.
I now happened to run into a situation where I need both NodeJS 14 and 18 installed. Any clever non-slotted workarounds available?
