postmodern
Add support for mruby mrbgems
Add support for mruby mrbgems. A possible way to do so would be to use the output from mgem config[1] to generate build_config.rb, although that requires installing mgem.
What if we allowed passing in the MRUBY_CONFIG variable?
ruby-install mruby -- MRUBY_CONFIG=/path/to/my/mruby_config.rb
Sounds simple, if it works i'm good with it. Would it be worth the trouble to consider mgem? Or is mgem too heavy dependency?
Having not used mgem, how does it integrate with mruby? It seems to only be used to generate the build_config.rb file?
mgem uses mgem-list repo to keep track of available gems.
mgem uses ~/.mgem/GEMS_ACTIVE.lst file to keep track of wanted gems,
then using mgem config to get build_config.rb (use mgem config default
if you don't want all the interactive questions).
That is what I know of mgem.
It sounds like mruby just needs a ./configure script to allow adding gems/gemboxes.
Played around with mruby and passing -- MRUBY_CONFIG=... should work. Also, we're considering dropping support for mruby since it's more suited for embedding into projects than installing globally. See #168