how crippled is ruby support in YP 3.0?
background: trying to get ruby and a number of ruby gems migrated
from "morty" to "zeus", and nothing but grief trying to compile/install ruby gems.
plan A: start with standard YP layers all checked out to "zeus", and
add vendor layer -- still similar grief.
current plan: start from absolute scratch, new project targetingx86_64, all layers checked out to "zeus", and build for core-image-minimal (*that* i know i can do).
then, little by little, add ruby content. has anyone here worked
with ruby and ruby gems extensively and has had to struggle to get stuff working? as soon as this basic build is done, i'm going to just add "ruby" to the image, and from there, start adding gems one by one.
should i expect this to go smoothly, or should i expect the pain
i've been through for the last couple days?
rday
Quoted 12 lines · Robert P. J. Day
background: trying to get ruby and a number of ruby gems migrated
from "morty" to "zeus", and nothing but grief trying to compile/install ruby gems.plan A: start with standard YP layers all checked out to "zeus",
and
add vendor layer -- still similar grief.current plan: start from absolute scratch, new project targeting
x86_64, all layers checked out to "zeus", and build for core-image-minimal (*that* i know i can do).
Quoted 8 lines
then, little by little, add ruby content. has anyone here worked
with ruby and ruby gems extensively and has had to struggle to get stuff working? as soon as this basic build is done, i'm going to just add "ruby" to the image, and from there, start adding gems one by one.should i expect this to go smoothly, or should i expect the pain
i've been through for the last couple days?
If we actually had some tests for it, we might have a much better idea.
The areas of the project with good automated tests tend not to regress without our noticing. Areas with no tests can and do :(
Cheers,
Richard
Quoted 5 lines · Richard Purdie
If we actually had some tests for it, we might have a much better idea.
The areas of the project with good automated tests tend not to regress without our noticing. Areas with no tests can and do :(
Not only that, the only reason ruby is in core at all is that webkit needs ruby-native. The interest in it is simply too low, but of course automated tests are welcome.
Alex