Reliance on $RBENV_ROOT being set about rbenv-communal-gems HOT 8 CLOSED

For the record, I cannot seem to figure out how to successfully communize my gems with this, even when exporting $RBENV_ROOT beforehand. Must be doing something wrong, but not sure how to diagnose considering it just says everything is successful.

from rbenv-communal-gems.

It should always be set by rbenv itself when it calls rbenv-communize. I saw this pattern in other plugins so something else must be wrong.

If you ls -ld .rbenv/versions/*/lib/ruby/gems, what do you get back?

from rbenv-communal-gems.

I suppose you could be right, though if it did I would expect it to still be set after running (though either way, it doesn't seem like I'm able to get it to work, set or not).

$ ls -ld .rbenv/versions/*/lib/ruby/gems
drwxr-xr-x  2 Acker  staff   68 Feb 24 20:03 .rbenv/versions/1.9.3-p385/lib/ruby/gems
drwxr-xr-x  3 Acker  staff  102 Feb 24 20:03 .rbenv/versions/1.9.3-p392/lib/ruby/gems

from rbenv-communal-gems.

Negative, it's in a subshell, so it won't propagate up.

What is the exact command you are running, and the exact output?

from rbenv-communal-gems.

Alright, I'll take your word on that.

$ gem list

*** LOCAL GEMS ***

bundler (1.2.4)
diff-lcs (1.2.1)
rbenv-gem-rehash (1.0.0)
rspec (2.13.0)
rspec-core (2.13.0)
rspec-expectations (2.13.0)
rspec-mocks (2.13.0)

$ rbenv communize --all
Communized gems for 1.9.3-p385
Communized gems for 1.9.3-p392

$ ls ~/.rbenv/gems/


$ ls -l ~/.rbenv/versions/1.9.3-p392/bin/gem/
-rwxr-xr-x  1 Acker  staff  577 Feb 24 19:09 /Users/Acker/.rbenv/versions/1.9.3-p392/bin/gem

$ gem list

*** LOCAL GEMS ***

rbenv-gem-rehash (1.0.0)

As far as I can tell, at this point I have lost all of my gems.

from rbenv-communal-gems.

Yes, it blows away the existing set rather than try to merge them in. What happens when you install a gem now?

from rbenv-communal-gems.

Aaah, I see, I must have been confused by the wording, I wasn't aware that it was going to completely remove that directory and it's contents, I was under the impression that it was going to move them, but I can see why it wouldn't do that now.

PEBKAC error, then. Seems to be all in order now. Perhaps just a little bit of clarification that it's going to delete the directory and it's contents, removing all current gems, on the readme?

(also, whoops on the close/reopen there, slipped and clicked close&comment before I was finished)

EDIT: probably made more of an issue for me because at the same time I got hit with the XCode update removing gcc and so when I tried to use this plugin I got tons of sudden missing gems and wasn't able to reinstall them properly after communizing.

I'll go ahead and close this now.

from rbenv-communal-gems.

Added an explicit rm -rf mention in the README.

from rbenv-communal-gems.