[ruby-core:122965] [Ruby Bug#21541] make install is failing due to using rdoc repo

Issue #21541 has been updated by st0012 (Stan Lo).


I think the best solution is to make sure `rdoc` always commit the generated files with CI checks verifying that they're up to date. `prism`, `rbs`, and `debug` (tho it's for readme) already do this and I don't see much issues caused by it.

----------------------------------------
Bug #21541: make install is failing due to using rdoc repo
https://bugs.ruby-lang.org/issues/21541#change-114269

* Author: MSP-Greg (Greg L)
* Status: Open
* ruby -v: master
* Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN
----------------------------------------
Currently, ruby-dev-builder & ruby-loco are failing due to https://github.com/ruby/ruby/commit/8f6f9e88c70bbae, which changed the rdoc 'bundled gem' install from using a released gem to the repo.  This results in an invalid rdoc installation.

RDoc contains *.ry and *.kpeg source files that need to be 'compiled' into *.rb files with racc and kpeg.

These *.rb files are not contained in the rdoc repo.

One possible change would be to have rdoc include the compiled *.rb files in its repo.  Puma has a similar issue with ragel files.  A GHA workflow (https://github.com/puma/puma/blob/master/.github/workflows/ragel.yml) checks that the compiled *.c file matches its respective *.rl source file.

Otherwise, a bit of code would be required in Ruby (and install of kpeg), or, rdoc must be installed from a released gem.



-- 
https://bugs.ruby-lang.org/
______________________________________________
 ruby-core mailing list -- [e-mail]
 To unsubscribe send an email to [e-mail]
 ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/