You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now dependencies on the compiler are screwed over by racc (runtime) having a faux-gemspec that ships with ruby. Splitting out the compiler would make it trivial to have a developer dependency on the compiler and a runtime dependency on the regular racc gem.
I'm (very) happy to do the work to split it out if this is approved.
The text was updated successfully, but these errors were encountered:
We generate a parser during development and commit it. Later we run tests in bundler. Prior to Ruby 3.3, the generated parser could always require racc since it was a default gem. But in 3.3 it's a bundled gem. So it needs to be added to our Gemfile when running tests.
One possible workaround I found is to use racc --embedded so that the racc runtime is inlined into the generated parser and we no longer have a runtime dependency on racc
Right now dependencies on the compiler are screwed over by racc (runtime) having a faux-gemspec that ships with ruby. Splitting out the compiler would make it trivial to have a developer dependency on the compiler and a runtime dependency on the regular racc gem.
I'm (very) happy to do the work to split it out if this is approved.
The text was updated successfully, but these errors were encountered: