Dne 11.5.2016 v 10:33 Vít Ondruch napsal(a): > 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?
The Foreman is still using it. Although there are some plans to remove it: http://projects.theforeman.org/issues/11449 http://projects.theforeman.org/issues/14809 Adding Dominic to CC. -- Miroslav Suchy, RHCA Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys _______________________________________________ ruby-sig mailing list [email protected] http://lists.fedoraproject.org/admin/lists/[email protected]
