Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

rbenv shouldn't display ruby's dependency #261

Closed
conradwt opened this Issue · 6 comments

4 participants

@conradwt

rbenv should only show rubies and not there underlying dependencies. For example, Maglev 1.0.0 depends on GemStone-27184.Darwin-i386


$ rbenv versions
  1.9.2-p320
* 1.9.3-p194 (set by /Users/conradwt/.rbenv/version)
  2.0.0-dev
  GemStone-27184.Darwin-i386
  jruby-1.7.0-preview2
  maglev-1.0.0
@mattneub

I believe rbenv versions simply lists what's at the top level of the ~/.rbenv/versions folder, so to avoid having something listed, don't put it there.

@conradwt

@mattneub I didn't put it there but this is where it was installed after invoking 'rbenv install maglev-1.0.0'.

@mattneub

Hmm, I see what you mean. Not sure what the right answer is for that.

@conradwt

@mattneub I'm not sure but this might be something that can be configured within rbenv or its plugin, ruby-build.

@guilleiguaran
Collaborator

@conradwt as you say, this should be handled in ruby-build no in rbenv, rbenv is just listing the content of ~/.rbenv/versions. Can you re-open this issue in ruby-build bug tracker?

Not sure but maybe the fix is avoid installation of GemStone in same folder of other rubies? Maybe @jc00ke can help us with this

@jc00ke

ruby-build could move the GemStone folder but it would have to update the symlinks in the maglev dir. I wouldn't recommend that. I would prefer filtering GemStone*/. out of the output. I realize this might not be ideal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.