I'll pull the trigger at Friday the 20th, if there is no
opposition (and there was no opposition so far).
Adding devel into the loop for wider audience.
Hi all,
I am thinking about retiring therubyracer from Fedora. Please
let me explain.
It was always pain to have therubyracer in Fedora. First
issue was to get it working with system v8. We did that, but
later, there were issues with compatibility after v8 updates.
Later, upstream split the v8 from therubyrace into separate
libv8 (!!!) rubygem, which made the situation even worse,
since I can't imagine to have rubyge-libv8-4.5.95.5 which will
use on the background different version of system v8. This
kept us with old version of therubyracer and old version of
v8. Recently, after introduction of gcc 6.x, there were some
issues with compilation of v8 and hence therubyracer was not
working. Now, Spot updated system v8 without asking into some
recent version, which is not compatible with our version of
therubyracer [1] and moreover, therubyracer upstream seems to
be stalled (there is no activity since September 2015 as far
as I can say).
We introduced therubyracer in the times, when NodeJS had not
been available in Fedora yet, when now it seems NodeJS is in
Fedora and does not go away any time soon.
Upcoming version of RHSCL are going to use NodeJS in place of
therubyracer as well.
All this means, that we should update all rubygems that needs
some JS engine to depends on NodeJS instead of therubyracer
and retire therubyracer.
Any thoughts?
Vít
[1] https://apps.fedoraproject.org/koschei/package/rubygem-therubyracer
-------- Přeposlaná zpráva --------
rubygem-therubyracer has broken dependencies in the rawhide tree:
On x86_64:
rubygem-therubyracer-0.11.0-13.fc24.x86_64 requires libv8.so.3()(64bit)
On i386:
rubygem-therubyracer-0.11.0-13.fc24.i686 requires libv8.so.3
On armhfp:
rubygem-therubyracer-0.11.0-13.fc24.armv7hl requires libv8.so.3
rubygem-therubyracer-0.11.0-13.fc24.armv7hl requires v8
Please resolve this as soon as possible.
_______________________________________________
ruby-sig mailing list
ruby-sig@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/ruby-sig@xxxxxxxxxxxxxxxxxxxxxxx
