Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#8266 - ruby; ri documentation not available
Attached to Project:
Arch Linux
Opened by Jan Smydke (crocus) - Tuesday, 09 October 2007, 10:49 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 10 October 2007, 03:16 GMT
Opened by Jan Smydke (crocus) - Tuesday, 09 October 2007, 10:49 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 10 October 2007, 03:16 GMT
|
Detailsruby documentation through ri not available.
I don't know whether the Arch developers decided not to include any documentation in the distribution, but this kind of convenient online built-in documentation for ruby is really inevitable for ruby-users. * package version ruby 1.8.6_p110-1 Steps to reproduce: 1) $ ri 'ERB' 2) $ irb > help 'ERB' |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Wednesday, 10 October 2007, 03:16 GMT
Reason for closing: Fixed
Additional comments about closing: version 1.8.6_p111-1 is in testing where this is fixed.
Wednesday, 10 October 2007, 03:16 GMT
Reason for closing: Fixed
Additional comments about closing: version 1.8.6_p111-1 is in testing where this is fixed.
perl, python and php don't include online documentation as well, same for gtk2&family devhelp and coreutils info pages.
The best way is to create ruby-docs package with documentation only, and put it in AUR.
"Actually it must be a problem of the binary pkg in repos, which doesn't contain the ri files. Simply rebuilding the VERY SAME package in abs (without any change) the ri files were present and ri works well as it used to. However still the binary in repo should be updated."
This is a valid point. If the PKGBUILD does not strip the ruby docs out, then it must be built wrong