FS#58104 - Ruby packages has all bundled gems stripped from it
Attached to Project:
Arch Linux
Opened by Tomas Volf (gray_-_wolf) - Wednesday, 04 April 2018, 16:20 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 04 April 2018, 16:31 GMT
Opened by Tomas Volf (gray_-_wolf) - Wednesday, 04 April 2018, 16:20 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 04 April 2018, 16:31 GMT
|
Details
Description:
Ruby package strips all bundled gems from it which causes problems when scripts expect bundled gems to be present. Issue https://github.com/hanami/hanami/issues/893 for example is caused by this, happens only on archlinux. What is the reasoning for stripping the gems like this? Does it actually has benefits except small saving in disk space (would argue mostly not relevant these days)? In my opinion the bundled gems should not be stripped from the package (since they are supposed to be always present). If they are stripped anyway, they should be at least made required dependencies for `ruby` package (again, since they are supposed to be always present). Failing even that, they should be at least all listed in optional dependecies with note saying `strongly recommended` or something. Please consider ^_^ Additional info: * ruby 2.5.0p0 (2017-12-25 revision 61468) [x86_64-linux] Steps to reproduce: 1. install ruby 2. clone hanami (https://github.com/hanami/hanami) 3. try to run it's setup script (./script/setup) <-- Fail due to missing builder |
This task depends upon
Closed by Doug Newgard (Scimmia)
Wednesday, 04 April 2018, 16:31 GMT
Reason for closing: Not a bug
Additional comments about closing: If you need the separate gems, install them.
Wednesday, 04 April 2018, 16:31 GMT
Reason for closing: Not a bug
Additional comments about closing: If you need the separate gems, install them.