On Wed, Jun 24, 2015 at 12:35 AM, Ben Woodcroft <[email protected]> wrote:
> Actually, I lie, this patch only sort of works. The issue is that it only
> works when a ruby package is also installed, GEM_PATH does not get set as
> part of the ruby-build-system for yaggo. The lib/ files are copied to what I
> gather is the correct place, but the env isn't right.
>
> The same also appears to be true of other ruby packages e.g. ruby-hoe:
This is the expected, correct behavior. The native search path
$GEM_PATH is defined in the ruby package, like so:
(native-search-paths
(list (search-path-specification
(variable "GEM_PATH")
(files (list (string-append "lib/ruby/gems/"
(version-major+minor version)
".0"))))))
Thus, you need ruby to be a part of your profile. Perhaps ruby should
be a propagated input for packages with ruby executables, or scripts
could be wrapped in another script that set the correct environment
variables.
- Dave
